Re: Evolving the D Language

2023-07-08 Thread harakim via Digitalmars-d-announce
On Friday, 7 July 2023 at 12:34:50 UTC, Hipreme wrote: The problem right now, from my POV, is that people such as Grim is using dub dependencies. What that generates is that by the default functionality being showing the deprecation messages is that we need to modify unmaintained 3rd party code

DScanner v0.16.0-beta.1 - looking for IDE dev feedback

2023-07-08 Thread WebFreak001 via Digitalmars-d-announce
https://github.com/dlang-community/D-Scanner/releases/tag/v0.16.0-beta.1 ## For IDE devs: the new D-Scanner version comes with a major new improvement: automatic fix suggestions for diagnostics. As IDE dev you can use the existing `--report` functionality to get JSON parsable output for the i

Re: Evolving the D Language

2023-07-08 Thread Jesse Phillips via Digitalmars-d-announce
On Friday, 7 July 2023 at 22:41:38 UTC, Walter Bright wrote: The problem has a lot to do with people wanting to use 3rd party libraries, and it being impractical to upgrade those libraries when the maintainer of those libraries is no longer active. If a user's project depends on several such li

Re: Evolving the D Language

2023-07-08 Thread Max Samukha via Digitalmars-d-announce
On Friday, 7 July 2023 at 10:45:33 UTC, Guillaume Piolat wrote: I don't remember people from outside the community being impressed by alias this. We have the right to backtrack on bad ideas instead of keeping them forever. I don't know why anybody should be impressed, but Zig and Jai, the tw

Re: Evolving the D Language

2023-07-08 Thread Olivier Pisano via Digitalmars-d-announce
On Friday, 7 July 2023 at 10:45:33 UTC, Guillaume Piolat wrote: On Friday, 7 July 2023 at 09:35:14 UTC, Paolo Invernizzi wrote: I respectfully disagree, and prefer to keep going on with the current deprecation and cleanup policy: Scott Meyers' DConf 2014 keynote all the way down. +1 I've a