On Thursday, 11 August 2016 at 22:07:57 UTC, Walter Bright wrote:
The scheme does not implement borrowing. References to internal
data should be returned via 'return ref' or 'return scope',
where their usage will be limited to the expression they appear
in.
I want to make sure we have the sam
On Thursday, 11 August 2016 at 22:03:02 UTC, Walter Bright wrote:
On 8/11/2016 6:38 AM, Sönke Ludwig wrote:
What would be nice to add is a behavior specification for
'scope' member
variables (lifetime considered equal or slightly shorter than
parent object
lifetime). For example the `RefCounted
On 8/12/2016 4:12 AM, Joseph Rushton Wakeling wrote:
On Thursday, 11 August 2016 at 22:07:57 UTC, Walter Bright wrote:
The scheme does not implement borrowing. References to internal data should be
returned via 'return ref' or 'return scope', where their usage will be limited
to the expression t
On Wednesday, 10 August 2016 at 20:35:23 UTC, Dicebot wrote:
The first DIP has just landed into the new queue. It is a
proposal from language authors and thus it bypasses usual
nitpicking process and proceeds straight to requesting
community (your!) feedback.
Thanks for all the work.
One rem
On Thursday, 11 August 2016 at 07:48:18 UTC, Walter Bright wrote:
On 8/10/2016 11:36 PM, rikki cattermole wrote:
Perfect :)
The nice thing about this scheme is it can do some things that
Rust can't (and Rust can do things that this can't). I suppose
it will balance out.
If this is successf
On Friday, 12 August 2016 at 12:01:41 UTC, Walter Bright wrote:
On 8/12/2016 4:12 AM, Joseph Rushton Wakeling wrote:
On Thursday, 11 August 2016 at 22:07:57 UTC, Walter Bright
wrote:
The scheme does not implement borrowing. References to
internal data should be
returned via 'return ref' or 'ret
On Friday, 12 August 2016 at 12:51:26 UTC, Joseph Rushton
Wakeling wrote:
I'm not sure I follow. I'm looking for the ability to
guarantee that a pointer to a stack-allocated entity will not
go out of scope
... more precisely, that the pointer will not become invalid
because the data it point
Rainer took some time out of his busy schedule to send me quite a
bit of information regarding the development of Visual D. The
post is now live at [1]. In the interest of space, I couldn't use
it all of his content. If anything feels unclear or disjointed,
that's on me and not Rainer.
For th
On Friday, 12 August 2016 at 14:27:48 UTC, Mike Parker wrote:
Rainer took some time out of his busy schedule to send me quite
a bit of information regarding the development of Visual D. The
post is now live at [1]. In the interest of space, I couldn't
use it all of his content. If anything feel
On Monday, 8 August 2016 at 04:24:45 UTC, Adam D. Ruppe wrote:
I decided to write up a think on untrapping exceptions this
week:
http://arsdnet.net/this-week-in-d/2016-aug-07.html
Next week I'll prolly talk about calling D from Ruby. Last
week, we had a status report from Stefan Koch on his C
On 11.08.2016 09:48, Walter Bright wrote:
On 8/10/2016 11:36 PM, rikki cattermole wrote:
Perfect :)
The nice thing about this scheme is it can do some things that Rust
can't
What are some of those things?
On 8/12/2016 5:54 AM, Joseph Rushton Wakeling wrote:
On Friday, 12 August 2016 at 12:51:26 UTC, Joseph Rushton Wakeling wrote:
I'm not sure I follow. I'm looking for the ability to guarantee that a
pointer to a stack-allocated entity will not go out of scope
... more precisely, that the point
On 8/12/2016 5:33 AM, Nordlöw wrote:
If this is successfully implemented, what will D not be able to do, that Rust
can/will?
Have ownership semantics for pointers in more complex data structures. In D
you'll have to do such with ref counted objects.
On the other hand, D code can reference mu
On 8/12/2016 12:03 PM, Timon Gehr wrote:
On 11.08.2016 09:48, Walter Bright wrote:
On 8/10/2016 11:36 PM, rikki cattermole wrote:
Perfect :)
The nice thing about this scheme is it can do some things that Rust
can't
What are some of those things?
Accessing mutable globals in a function com
On 8/12/2016 5:24 AM, Nordlöw wrote:
On Wednesday, 10 August 2016 at 20:35:23 UTC, Dicebot wrote:
The first DIP has just landed into the new queue. It is a proposal from
language authors and thus it bypasses usual nitpicking process and proceeds
straight to requesting community (your!) feedback.
On 12.08.2016 21:39, Walter Bright wrote:
On 8/12/2016 5:33 AM, Nordlöw wrote:
If this is successfully implemented, what will D not be able to do,
that Rust
can/will?
Have ownership semantics for pointers in more complex data structures.
In D you'll have to do such with ref counted objects.
O
On 8/12/2016 1:08 PM, Timon Gehr wrote:
On 12.08.2016 21:39, Walter Bright wrote:
On 8/12/2016 5:33 AM, Nordlöw wrote:
If this is successfully implemented, what will D not be able to do,
that Rust
can/will?
Have ownership semantics for pointers in more complex data structures.
In D you'll hav
On Friday, 12 August 2016 at 17:00:31 UTC, Radu wrote:
Mike,
Just wanted to say you are doing an awesone work with your blog
posts, greatly appreciated!
Many thanks for Rainer's hard work also. Visual D is a very
important piece of the D language ecosystem and something I use
with pleasure
18 matches
Mail list logo
