On Saturday, 18 May 2019 at 01:24:35 UTC, Vladimir Panteleev
wrote:
On Friday, 17 May 2019 at 06:25:23 UTC, Suliman wrote:
Waterfox 56.2.9
Oh! I used on my site new js future. It will work after
updating browser.
Waterfox 56.2.9 is currently the latest version of Waterfox.
There is no
On Friday, 17 May 2019 at 06:25:23 UTC, Suliman wrote:
Waterfox 56.2.9
Oh! I used on my site new js future. It will work after
updating browser.
Waterfox 56.2.9 is currently the latest version of Waterfox.
There is no newer version to update to.
Waterfox uses an older version of Gecko
On Friday, 17 May 2019 at 21:57:51 UTC, Meta wrote:
I see what you're getting at. The compiler sees a slice type
(i.e., Data[]), knows that it's GC-backed and thus has infinite
lifetime, and concludes "the data you're trying to put in the
store has too long of a lifetime".
Should be "too
On Friday, 17 May 2019 at 18:45:12 UTC, Jonathan M Davis wrote:
On Friday, May 17, 2019 11:25:40 AM MDT Meta via
Digitalmars-d-announce wrote:
I don't want to *restrict* the lifetime of a heap allocation.
I want the compiler to recognize that the lifetime of my
original data is the same as the
On Friday, 17 May 2019 at 20:59:43 UTC, Mike Franklin wrote:
On Friday, 17 May 2019 at 17:03:51 UTC, Meta wrote:
If you look at `main` above, `rawData` has the same lifetime
as the `dataRange` struct returned from `makeDataRange` and
the queue returned from `copyToQueue`. True, there is some
On Friday, 17 May 2019 at 20:59:43 UTC, Mike Franklin wrote:
I don't think it does because `Queue!(T).store` has infinite
lifetime beyond that of even `main`, at least as far as the
compiler is concerned. The compiler doesn't have enough
information to know that `store` is tied to the
On Friday, 17 May 2019 at 17:03:51 UTC, Meta wrote:
If you look at `main` above, `rawData` has the same lifetime as
the `dataRange` struct returned from `makeDataRange` and the
queue returned from `copyToQueue`. True, there is some
traditionally unsafe stuff happening in between; however, I
On 5/17/2019 11:45 AM, Jonathan M Davis wrote:
It is my understanding that DIP 1000 really doesn't track lifetimes at all.
It just ensures that no references to the data escape. So, you can't do
something like take a scope variable and put any references to it or what it
refers to in a
On 5/17/2019 10:26 AM, Meta wrote:
I'll try to reduce it further, but this example is already as reduced as I could
make it while still having the same structure as my actual code.
It doesn't need to have the same structure. It just needs to exhibit the
problem.
On Friday, May 17, 2019 11:25:40 AM MDT Meta via Digitalmars-d-announce
wrote:
> I don't want to *restrict* the lifetime of a heap allocation. I
> want the compiler to recognize that the lifetime of my original
> data is the same as the processed output, and thus allow my code
> to compile.
It
On 17.05.19 19:25, Meta wrote:
I don't want to *restrict* the lifetime of a heap allocation. I want the
compiler to recognize that the lifetime of my original data is the same
as the processed output, and thus allow my code to compile.
You have a heap allocation that references your original
On Friday, 17 May 2019 at 05:27:02 UTC, Walter Bright wrote:
On 5/16/2019 9:50 PM, Meta wrote:
Walter, can I get you to take a look at this post I made a few
months ago, and the contained example? I feel that this is a
case that *should* definitely work, but I'm not sure if it can
*currently*
On Friday, 17 May 2019 at 17:05:21 UTC, ag0aep6g wrote:
On 17.05.19 14:10, Meta wrote:
Your explanation was fine, but I need a good solution, other
than wrapping the array assignment in @trusted.
I see. As far as I understand DIP 1000, it's not supposed to
enable your use case without having
On 17.05.19 14:10, Meta wrote:
Your explanation was fine, but I need a good solution, other than
wrapping the array assignment in @trusted.
I see. As far as I understand DIP 1000, it's not supposed to enable your
use case without having to use `@trusted`.
DIP 1000 stops at heap allocations.
On Friday, 17 May 2019 at 05:32:42 UTC, Mike Franklin wrote:
On Friday, 17 May 2019 at 05:22:30 UTC, Mike Franklin wrote:
My assessment (which could be wrong):
`scope` and `return` only apply to pointers and `ref`s. If
you remove all `scope` and `return` attributes from the
function `push`,
On Friday, 17 May 2019 at 15:41:30 UTC, dayllenger wrote:
On Friday, 17 May 2019 at 13:39:35 UTC, drug wrote:
First of all, you are totally wrong.
Crimea ...
It's not a fact, it's just your opinion, very similar to one
that russian federal TV transmits.
And the last but no least - nobody
On Friday, 17 May 2019 at 13:39:35 UTC, drug wrote:
First of all, you are totally wrong.
Crimea ...
It's not a fact, it's just your opinion, very similar to one that
russian federal TV transmits.
And the last but no least - nobody suppresses me or my friends
in Russia. Have you ever been
On 17.05.2019 15:13, ikod wrote:
At least he leaded Crimea annexion, war against Georgia, current proxy
war on the east of Ukraine. He pretend to defend russians outside of the
Russia, but suppress them in their own country.
Well, I let myself to talk a little bit about your statement.
First
On Friday, 17 May 2019 at 05:22:31 UTC, ag0aep6g wrote:
On 17.05.19 06:50, Meta wrote:
Walter, can I get you to take a look at this post I made a few
months ago, and the contained example? I feel that this is a
case that *should* definitely work, but I'm not sure if it can
*currently* work -
On Friday, 17 May 2019 at 08:14:26 UTC, drug wrote:
I understand that there is a habit to guilt Russians and/or
Putin in many problems but let's try to be clever?
At least he leaded Crimea annexion, war against Georgia, current
proxy war on the east of Ukraine. He pretend to defend russians
On Thursday, 16 May 2019 at 21:21:50 UTC, Iain Buclaw wrote:
Hi,
Another year, another site update. This syncs with the latest
gcc-explorer, and refreshes all compilers to version 9.1.
This time around, I've built 190 (one-hundred-and-ninety) D
compilers, each for a different target
On 17.05.2019 12:54, Suliman wrote:
Try to solve your problems by yourself
How?
My regrets that I don't provide step-by-step instruction but you can do
something like others thousands of sites in "ru" domain do. You probably
don't believe me but every day I visit tens of Russian sites without
Try to solve your problems by yourself
How?
On Thursday, May 16, 2019 11:22:30 PM MDT Mike Franklin via Digitalmars-d-
announce wrote:
> I consider it a bug that the compiler doesn't emit an error when
> using attributes on types for which they are not intended.
As in you think that something like
auto foo(scope int i) {...}
should be
On 17.05.2019 10:16, Suliman wrote:
On Friday, 17 May 2019 at 06:46:06 UTC, DanielG wrote:
On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote:
P.S. site is blocked by most of russian internet-providers by RKN
Why is that?
This organization is created by Putin's friends. It's purpose
On Friday, 17 May 2019 at 06:46:06 UTC, DanielG wrote:
On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote:
P.S. site is blocked by most of russian internet-providers by
RKN
Why is that?
I've fallen quite far behind on my email correspondence in the
past two weeks. I'm decompressing from some serious jet lag right
now, but I've begun trying to catch up. If you've emailed me
recently and receive no reply by the end of this weekend, please
ping me.
On Friday, 17 May 2019 at 06:46:06 UTC, DanielG wrote:
On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote:
P.S. site is blocked by most of russian internet-providers by
RKN
Why is that?
This organization is created by Putin's friends. It's purpose to
block all opposition, but they do
On Thursday, 16 May 2019 at 12:25:52 UTC, Suliman wrote:
P.S. site is blocked by most of russian internet-providers by
RKN
Why is that?
Waterfox 56.2.9
Oh! I used on my site new js future. It will work after updating
browser.
30 matches
Mail list logo
