ekuber, 1 month ago Somewhat cursed #RustLang idea: "attributes at a distance" #![attr(target = crate::foo::Bar)] mod foo { struct Bar; } What would you use this for?
Somewhat cursed #RustLang idea: "attributes at a distance"
#![attr(target = crate::foo::Bar)] mod foo { struct Bar; }
What would you use this for?
muvlon, 1 month ago @ekuber Why of course to derive traits on foreign types 😈 Life's too short for coherence!
@ekuber Why of course to derive traits on foreign types 😈
Life's too short for coherence!
ekuber, 1 month ago @muvlon I have been accused of being incoherent in the past 😋
@muvlon I have been accused of being incoherent in the past 😋
jhpratt, 1 month ago @ekuber Allowing something deprecated is an obvious situation to me
@ekuber Allowing something deprecated is an obvious situation to me
ekuber, 1 month ago @jhpratt you're thinking an "allow in this project the use of this explicit deprecated item"? That seems like a good argument for lint arguments.
@jhpratt you're thinking an "allow in this project the use of this explicit deprecated item"? That seems like a good argument for lint arguments.
jhpratt, 1 month ago @ekuber Ah, I misunderstood what was being suggested. I have no idea why you'd want that 😅
@ekuber Ah, I misunderstood what was being suggested. I have no idea why you'd want that 😅
ekuber, 1 month ago @jhpratt 😄 None of the reasons that come to mind are non-horrifying
@jhpratt 😄 None of the reasons that come to mind are non-horrifying
ekuber, 1 month ago The idea came in the context of lints, after looking at how C# deals with them, the following is expressible there: #![allow("unused", target = crate::foo::Bar)] mod foo { struct Bar; }
The idea came in the context of lints, after looking at how C# deals with them, the following is expressible there:
#![allow("unused", target = crate::foo::Bar)] mod foo { struct Bar; }
mo8it, 1 month ago @ekuber It will lead to a lot of confusion for no significant win. Effects that are very hard to track back.
@ekuber It will lead to a lot of confusion for no significant win. Effects that are very hard to track back.
ekuber, 1 month ago @mo8it be aware that with proc-macros and build files you can commit multiple non-locality crimes today 😬
@mo8it be aware that with proc-macros and build files you can commit multiple non-locality crimes today 😬
Add comment