Various cleanups of macro-expanding-to-module workarounds #10719
Conversation
src/libstd/c_str.rs
Outdated
There was a problem hiding this comment.
This isn't removing a macro work-around, right? Would it be possible to have the macro stuff and the #5922 stuff in separate commits?
There was a problem hiding this comment.
They both meet in the VecIterator implementation macro. Separating them would mean introducing additional changes just to remove them again in the next commit.
There was a problem hiding this comment.
Probably worth at least mentioning that you're removing some dummy fields that gives structs lifetimes in the PR text/commit message.
There was a problem hiding this comment.
Hm, also, #10703 probably means it's too early to remove them now, as it will allow people to write invalid/unsafe/crashing code.
Also documented a few issues
src/libstd/num/int_macros.rs
Outdated
There was a problem hiding this comment.
This should remove the previous FIXME because it's no longer an open issue. I would personally be ok with just copy-pasting all of the attributes/include statements in each of the files using this macro (it's a big step forward in having reasonable documentation for these modules)
There was a problem hiding this comment.
Okay, will do that then
…excrichton
- Removed module reexport workaround for the integer module macros
- Removed legacy reexports of `cmp::{min, max}` in the integer module macros
- Combined a few macros in `vec` into one
- Documented a few issues
…, r=jonas-schievink Restart proc-macro client when server reload Fix rust-lang#10719
…rted_modules, r=Alexendoo Fix `items_after_test_module`: Ignore imported modules Fixes rust-lang#10713. It does a little bit of dark magic, but intention is what really counts. changelog:[`items_after_test_module`]: Ignore imported modules (`mod foo;`) with no body.
4 participants
cmp::{min, max}in the integer module macrosvecinto one