bonjour, ex:
std.unicode.Decode
As far as I’m concerned, I learned about this while reading on the forum.
I’ve corrected it, but if there was an order when compiling to point it out, I’d like it.
currently when something is gets deprecated
- its the first thing in the doc comment
- next release is changed to a
@compileError - next next release is removed
@deprecated isnt done yet but it should be in 0.14.1 or 0.15.0
it should make this a lot better as it will give you a deprecated build error but still allow dependencies to use them
1 Like