On 2019-09-17 22:55, Johan Engelen wrote:
Wow. How come this is not caught by the CI testing?
That issue seems to be because "writeln" is printing "type", which is an
enum. For enums, "writeln" prints the actual name of the enum member and
not the value. It seems it extracts the names of
On 9/18/19 11:09 AM, H. S. Teoh wrote:
On Wed, Sep 18, 2019 at 10:48:27AM -0400, Steven Schveighoffer via
Digitalmars-d-learn wrote:
On 9/17/19 8:14 PM, Jonathan M Davis wrote:
[...]
I suspect that deprecation messages are being triggered simply by
code trying to use Nullable in template
On Wed, Sep 18, 2019 at 10:48:27AM -0400, Steven Schveighoffer via
Digitalmars-d-learn wrote:
> On 9/17/19 8:14 PM, Jonathan M Davis wrote:
[...]
> > I suspect that deprecation messages are being triggered simply by
> > code trying to use Nullable in template constraints rather than just
> > when
On 9/17/19 8:14 PM, Jonathan M Davis wrote:
On Tuesday, September 17, 2019 2:34:00 PM MDT Steven Schveighoffer via
Digitalmars-d-learn wrote:
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
On Tuesday, September 17, 2019 2:34:00 PM MDT Steven Schveighoffer via
Digitalmars-d-learn wrote:
> 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
> >>
On Tuesday, September 17, 2019 5:28:33 PM MDT H. S. Teoh via Digitalmars-d-
learn wrote:
> On Tue, Sep 17, 2019 at 08:55:27PM +, Johan Engelen via
> Digitalmars-d-learn wrote: [...]
>
> > Wow. How come this is not caught by the CI testing?
>
> [...]
>
> Is the CI setup to detect deprecations
On Tue, Sep 17, 2019 at 08:55:27PM +, Johan Engelen via Digitalmars-d-learn
wrote:
[...]
> Wow. How come this is not caught by the CI testing?
[...]
Is the CI setup to detect deprecations and flag them as failures?
It's either that, or many cases are not tested because Phobos has a lot
of
On 9/17/19 3:31 PM, Steven Schveighoffer wrote:
Hi,
I just upgraded my compiler from 2.084 to 2.088, and I'm getting scores
of deprecation messages. One thing I've realized is that most of these
messages are generated by calls outside my code. These deprecation
messages are intended to tell
On Tuesday, 17 September 2019 at 20:16:12 UTC, 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,
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
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.
Hi,
I just upgraded my compiler from 2.084 to 2.088, and I'm getting scores
of deprecation messages. One thing I've realized is that most of these
messages are generated by calls outside my code. These deprecation
messages are intended to tell you where you are calling them, but end up
12 matches
Mail list logo
