Thread overview | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
September 29, 2020 Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Hi folks, I've this: /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly. I'm trying to find out WHERE this is generated to fix it, dependency included, without success. Suggestions? |
September 29, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Frak | On 9/29/20 1:08 PM, Frak wrote:
> Hi folks,
>
> I've this:
>
> /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly.
>
> I'm trying to find out WHERE this is generated to fix it, dependency included, without success.
>
> Suggestions?
Because it's probably coming from a constraint, you probably can't figure out the exact usage. What's more annoying is that likely it is a spurious warning. A lot of traits "try something", and then alias to false or true depending on what works. But it's not going to make a difference in your code.
It's one of the most annoying things in the library. If you see this warning coming from *your* code, then you should fix it. But it will tell you the location if that was the case, not std.traits.
-Steve
|
September 29, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Frak | On 9/29/20 10:08 AM, Frak wrote:
> Hi folks,
>
> I've this:
>
> /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly.
>
> I'm trying to find out WHERE this is generated to fix it, dependency included, without success.
>
> Suggestions?
I've just ported my code to 2.094 and had to clean up that issue. Luckily, in my case they were all in user code. I had to access my Nullable objects with .get:
if (n) {
// n.foo(); <-- from
n.get.foo(); <-- to
}
So, look at all your Nullable objects maybe.
Ali
|
September 30, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Steven Schveighoffer | On Tuesday, 29 September 2020 at 18:25:03 UTC, Steven Schveighoffer wrote:
> On 9/29/20 1:08 PM, Frak wrote:
>> Hi folks,
>>
>> I've this:
>>
>> /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly.
>>
>> I'm trying to find out WHERE this is generated to fix it, dependency included, without success.
>>
>> Suggestions?
>
> Because it's probably coming from a constraint, you probably can't figure out the exact usage. What's more annoying is that likely it is a spurious warning. A lot of traits "try something", and then alias to false or true depending on what works. But it's not going to make a difference in your code.
>
> It's one of the most annoying things in the library. If you see this warning coming from *your* code, then you should fix it. But it will tell you the location if that was the case, not std.traits.
>
> -Steve
That's REALLY REALLY annoying! I'm spending LOT of time trying to figure out the exact point to fix in the code.
Any idea? dustmite?
|
September 30, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Frak | On Wednesday, 30 September 2020 at 08:33:58 UTC, Frak wrote:
> On Tuesday, 29 September 2020 at 18:25:03 UTC, Steven Schveighoffer wrote:
>> On 9/29/20 1:08 PM, Frak wrote:
>>> [...]
>>
>> Because it's probably coming from a constraint, you probably can't figure out the exact usage. What's more annoying is that likely it is a spurious warning. A lot of traits "try something", and then alias to false or true depending on what works. But it's not going to make a difference in your code.
>>
>> It's one of the most annoying things in the library. If you see this warning coming from *your* code, then you should fix it. But it will tell you the location if that was the case, not std.traits.
>>
>> -Steve
>
> That's REALLY REALLY annoying! I'm spending LOT of time trying to figure out the exact point to fix in the code.
>
> Any idea? dustmite?
You can give me access to the code and I can find it out for you.
That's the best I have.
|
September 30, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Stefan Koch | On Wednesday, 30 September 2020 at 09:42:40 UTC, Stefan Koch wrote:
> On Wednesday, 30 September 2020 at 08:33:58 UTC, Frak wrote:
>> On Tuesday, 29 September 2020 at 18:25:03 UTC, Steven Schveighoffer wrote:
>>> On 9/29/20 1:08 PM, Frak wrote:
>>>> [...]
>>>
>>> Because it's probably coming from a constraint, you probably can't figure out the exact usage. What's more annoying is that likely it is a spurious warning. A lot of traits "try something", and then alias to false or true depending on what works. But it's not going to make a difference in your code.
>>>
>>> It's one of the most annoying things in the library. If you see this warning coming from *your* code, then you should fix it. But it will tell you the location if that was the case, not std.traits.
>>>
>>> -Steve
>>
>> That's REALLY REALLY annoying! I'm spending LOT of time trying to figure out the exact point to fix in the code.
>>
>> Any idea? dustmite?
>
> You can give me access to the code and I can find it out for you.
> That's the best I have.
Thank you, but unfortunately that's not possible
|
September 30, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Frak | On Tuesday, 29 September 2020 at 17:08:40 UTC, Frak wrote: > Hi folks, > > I've this: > > /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly. > > I'm trying to find out WHERE this is generated to fix it, dependency included, without success. > > Suggestions? The problem has been observed already and it is an official enhancement request [1]. I think it is legit because deprecation are sometimes used to help into refactoring, so to have the use site is a essential. [1] https://issues.dlang.org/show_bug.cgi?id=21176 |
September 30, 2020 Re: Deprecation in traits | ||||
---|---|---|---|---|
| ||||
Posted in reply to Basile B. | On Wednesday, 30 September 2020 at 18:18:48 UTC, Basile B. wrote:
> On Tuesday, 29 September 2020 at 17:08:40 UTC, Frak wrote:
>> Hi folks,
>>
>> I've this:
>>
>> /Users/frak/dlang/ldc-1.23.0/bin/../import/std/traits.d(3711): Deprecation: function `std.typecons.Nullable!long.Nullable.get_` is deprecated - Implicit conversion with `alias Nullable.get this` will be removed after 2.096. Please use `.get` explicitly.
>>
>> I'm trying to find out WHERE this is generated to fix it, dependency included, without success.
>>
>> Suggestions?
>
> The problem has been observed already and it is an official enhancement request [1].
> I think it is legit because deprecation are sometimes used to help into refactoring, so to have the use site is a essential.
>
> [1] https://issues.dlang.org/show_bug.cgi?id=21176
Does compiling with -v help? I think it might at least show you which module the issue is coming from?
|
Copyright © 1999-2021 by the D Language Foundation