Tell us your DIP1000 woes

Mike Parker aldacron at gmail.com
Sun Aug 25 13:10:22 UTC 2024


DIP1000 keeps rearing its head in discussions touching on safety 
in our monthly meetings. So we recently held a planning session 
focused exclusively on DIP1000. Two things came out of it.

First, it's pretty clear that inference by default is necessary 
to make DIP1000 easier to use. It's not clear at the moment how 
this can be achieved, but it's something that we need to work out.

Second, we'd like to get a number of examples of problems people 
have had with using DIP1000 that haven't shown up in Bugzilla. 
Walter wants to be as certain as he can whether such issues are 
fixable or if the design is fundamentally flawed.

If you've had problems using DIP1000, please post here with a 
description of what you encountered and any details about it you 
think we may find helpful. Please provide example code where 
possible.

As an example of the sort of thing we're looking for, someone in 
the meeting brought up the problems encountered with trying to 
add DIP1000 support to vibe.d.

**Please do not reply to posts in this thread unless you have 
additional relevant information regarding the problem 
described.** We want to collect examples, and any side 
discussions will just be noise.

Thanks!




More information about the Digitalmars-d mailing list