https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #23 from github-bugzi...@puremagic.com ---
Commit pushed to stable at https://github.com/D-Programming-Language/dmd
https://github.com/D-Programming-Language/dmd/commit/53c5b59ca83e471fea6e4464862b39e62df0f335
Merge pull request #4458
https://issues.dlang.org/show_bug.cgi?id=14232
Andrei Alexandrescu and...@erdani.com changed:
What|Removed |Added
Version|unspecified |D2
--
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #22 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/D-Programming-Language/dmd
https://github.com/D-Programming-Language/dmd/commit/9edd2223950b919a201cf104601f877283cca2bf
Merge pull request #4458
from
mihails-strasuns-sociomantic/redundant-attrib-deprec
[REG] fix Issue 14232 : redundant attribute 'const'
--
from
mihails-strasuns-sociomantic/redundant-attrib-deprec
[REG] fix Issue 14232 : redundant attribute 'const'
--
https://issues.dlang.org/show_bug.cgi?id=14232
github-bugzi...@puremagic.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #19 from Dicebot pub...@dicebot.lv ---
https://github.com/D-Programming-Language/dmd/pull/4458
--
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #8 from Martin Nowak c...@dawg.eu ---
(In reply to Ketmar Dark from comment #7)
so do you mean that if some syntax was allowed by accident, it should be
kept forever
No it should be kept for one release with a deprecation warning
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #11 from Ketmar Dark ket...@ketmar.no-ip.org ---
but why? it's not the compiler task to babysit old and broken code, it's
lint(dfix) task. removing that burden from compiler allows alot more
possibilities, as compiler code stays clean,
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #9 from Dicebot pub...@dicebot.lv ---
It was introduced in 1b932b9282df6ed312b6da0031417ea0d4f8faa5
I am looking in how deprecation message can be added
--
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #12 from Dicebot pub...@dicebot.lv ---
Can you please resist the temptation to start another pointless discussion with
ketmar? I don't want to disable notifications for this issue.
--
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #10 from Martin Nowak c...@dawg.eu ---
(In reply to Ketmar Dark from comment #7)
Once dfix is ready for primetime and is release with dmd we might switch to a
model where we such changes are accompanied with a rewrite in dfix. But for
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #13 from Martin Nowak c...@dawg.eu ---
Thanks @dicebot.
It's this error you're triggering.
https://github.com/9rnsr/dmd/commit/1b932b9282df6ed312b6da0031417ea0d4f8faa5#diff-62dcb5f0ffc3089b7565897d8beb3322R918
At best you pass a `bool
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #15 from Martin Nowak c...@dawg.eu ---
(In reply to Ketmar Dark from comment #11)
i'm far from saying that nothing should be done. actually, i'm saying the
exact opposite thing: it's time to bless dfix and bundle it with compiler
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #14 from Dicebot pub...@dicebot.lv ---
Thanks, working on it.
--
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #17 from Kenji Hara k.hara...@gmail.com ---
(In reply to Martin Nowak from comment #4)
(In reply to Ketmar Dark from comment #3)
should any bug be deprecated first — just in case somebody wrote invalid
code relying on that bug?
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #16 from Ketmar Dark ket...@ketmar.no-ip.org ---
How about you work with Brian on getting it integrated for 2.068?
i've never seen a call for help from him. but sure, if he needs any help i can
provide, i'm ready to do that... after dfix
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #18 from Martin Nowak c...@dawg.eu ---
(In reply to Kenji Hara from comment #17)
Accepting redundant attributes had not been documented in language spec, it
has been just accidentally accepted. Therefore, consistently disabling them
https://issues.dlang.org/show_bug.cgi?id=14232
Dicebot pub...@dicebot.lv changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #7 from Ketmar Dark ket...@ketmar.no-ip.org ---
so do you mean that if some syntax was allowed by accident, it should be kept
forever, shitting compiler code with hacks over hacks trying to accept both
valid code and invalid code?
no,
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #1 from Kenji Hara k.hara...@gmail.com ---
The following program already reported same error in 2.066:
struct Bug
{
const const void bug()
{
}
}
test.d(3): Error: redundant attribute 'const'
--
https://issues.dlang.org/show_bug.cgi?id=14232
Ketmar Dark ket...@ketmar.no-ip.org changed:
What|Removed |Added
CC||ket...@ketmar.no-ip.org
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #5 from Ketmar Dark ket...@ketmar.no-ip.org ---
this effectively turns compiler code to unmaintainable spaghetti. and i believe
that this is the perfect application for lint-like tool (yes, devs can finally
bless dfix). with dfix blessed
https://issues.dlang.org/show_bug.cgi?id=14232
briancsch...@gmail.com changed:
What|Removed |Added
CC||briancsch...@gmail.com
--- Comment
https://issues.dlang.org/show_bug.cgi?id=14232
--- Comment #4 from Martin Nowak c...@dawg.eu ---
(In reply to Ketmar Dark from comment #3)
should any bug be deprecated first — just in case somebody wrote invalid
code relying on that bug?
Usually yes, but within reason, depending on how
https://issues.dlang.org/show_bug.cgi?id=14232
Martin Nowak c...@dawg.eu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
26 matches
Mail list logo
