Deprecation message sources
Steven Schveighoffer
schveiguy at gmail.com
Tue Sep 17 20:34:00 UTC 2019
On 9/17/19 4:16 PM, Anonymouse wrote:
> On Tuesday, 17 September 2019 at 19:31:53 UTC, Steven Schveighoffer wrote:
>> I'd hate to say the answer is to special case Nullable for so many
>> functions, but what other alternative is there?
>>
>> -Steve
>
> Nullable isn't alone, std.json.JSONType causes a literal wall of text of
> deprecation warnings.
>
> import std.stdio;
> import std.json;
>
> void main()
> {
> writeln(JSONValue.init.type);
> }
>
> https://run.dlang.io/is/J0UDay
I mean, I'm OK with the idea, but having these deprecation messages is
helping nobody. I can't figure out if there's something I'm supposed to,
or can, change in order to get rid of them.
There are quite a few places where it is flagging my code for Nullable
usage without get, and I'm fixing those. But I'll still be left with
this mess of deprecation messages from Phobos and vibe.d. I don't even
know where or if it will break once the alias this is removed.
-Steve
More information about the Digitalmars-d-learn
mailing list