Re: DIP1000: Scoped Pointers

2016-08-14 Thread Walter Bright via Digitalmars-d-announce

On 8/14/2016 9:56 PM, Joseph Rushton Wakeling wrote:

Does that actually work in D2?


Yes.



Re: DIP1000: Scoped Pointers

2016-08-14 Thread Joseph Rushton Wakeling via Digitalmars-d-announce
On Sunday, 14 August 2016 at 10:11:25 UTC, Guillaume Chatelet 
wrote:

Isn't it what a scoped class is supposed to provide?

class Rnd {}

void foo() {
  scope rnd  = new Rnd; // reference semantic and stack 
allocated

}


Does that actually work in D2? I thought it was a D1-only thing.



Re: Battle-plan for CTFE

2016-08-14 Thread Rory McGuire via Digitalmars-d-announce
On Sun, Aug 14, 2016 at 5:21 AM, Stefan Koch via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:

> Hi,
>
> I took a break from work on string operations and focused instead of
> improving the robustness of the engine.
> I.E. for it not to halt the compiler on unsupported expressions.
>
> right now,
> I can compile druntime without failures.
> Phobos should be working by the end of next week.
>
> Have a nice Sunday,
>
> Stefan
>
> PS. String foreach regressed.
> And Struct-handling regressed.
> Due to a change of memory-layout.
>
> I will fix this as soon as the engine does no longer abort.
>
>
Nice! thanks! Will be nice to be able to test newCTFE with our "normal"
code every now and then.


Re: DIP1000: Scoped Pointers

2016-08-14 Thread Guillaume Chatelet via Digitalmars-d-announce
On Saturday, 13 August 2016 at 20:50:53 UTC, Joseph Rushton 
Wakeling wrote:
The TL;DR here is that I'm concerned about having a solution 
for random number generators and random algorithms that (i) 
allows them to be stack-allocated, (ii) ensures that their 
internal state is not accidentally copied by value, and (iii) 
allows them to work effectively with (input) range semantics.


Isn't it what a scoped class is supposed to provide?

class Rnd {}

void foo() {
  scope rnd  = new Rnd; // reference semantic and stack allocated
}