default implemented opAssign purity
Dan
dbdavidson at yahoo.com
Sun Dec 2 14:27:26 PST 2012
On Sunday, 2 December 2012 at 22:19:18 UTC, Jonathan M Davis
wrote:
> On Sunday, December 02, 2012 23:04:29 Dan wrote:
> What about the specification is lax? pure, const, and immutable
> are quite well
> defined.
Sorry - by specification I was not thinking D Language
Specification but more API or library specification. More
accurately I should have said lax signatures.
> The problem here is that it's stuff in druntime that needs to
> be fixed
> which very few people can do, and it often runs into other
> problems which
> makes making any of the changes incredibly difficult. For
> instance, to fix the
> current AA implementation requires a ton of work, because it
> affects all kinds
> of stuff all over the place in druntime, so the result is that
> none of it is
> getting fixed right now, which obviously isn't good.
>
Fair enough.
> Some of this stuff is getting fixed incrementally, but it's
> definitely taking
> longer than would be desirable, and while some of it may be low
> hanging fruit,
> a lot of it really isn't because of how much stuff is affected.
> Small changes
> quickly become huge ones when dealing with druntime changes -
> especially with
> stuff like pure, const, and nothrow.
>
More information about the Digitalmars-d-learn
mailing list