3 ms·
I understand the suggestion, and adding a guard to the knife makes some sense, but where's the line? As a library developer, let's say I use a few implicit con
by CriasSK 15y ago
I understand the suggestion, and adding a guard to the knife makes some sense, but where's the line?
As a library developer, let's say I use a few implicit conversions to make my library easy to use. I sign off on the use with a compiler flag, no big deal, but now every user of my library has to do the same?
Perhaps I'm misunderstanding, but wouldn't this suggestion effectively ruin "ArrowAssoc"? Because I can't think of a single application I write that doesn't use one of those, honestly.
- modersky 15y agoI am thinking only of putting (some) definitions of implicit conversions behind a compiler flag. Uses of such conversions would remain unaffected.