Conversation
|
Do we want to perhaps go ahead and merge |
|
@alexcrichton that is kind of tricky because everything in proc_macro_tokens uses the |
|
@bors: r+ Ok! |
|
📌 Commit f3f3af8 has been approved by |
|
⌛ Testing commit f3f3af8 with merge db1ca00... |
|
💔 Test failed - auto-linux-cross-opt |
|
📌 Commit c4f05d9 has been approved by |
|
⌛ Testing commit c4f05d9 with merge d4def4d... |
|
💔 Test failed - auto-win-msvc-64-opt-rustbuild |
|
📌 Commit 198215a has been approved by |
Split up libproc_macro_plugin Separate the plugin code from non-plugin code to break a potential cycle in crates. This will allow us to merge the new libproc_macro_tokens into libproc_macro. r? @alexcrichton
|
💔 Test failed - auto-win-msvc-32-opt |
Separate the plugin code from non-plugin code to break a potential cycle in crates. This will allow us to merge the new libproc_macro_tokens into libproc_macro.
|
📌 Commit 15821ca has been approved by |
Split up libproc_macro_plugin Separate the plugin code from non-plugin code to break a potential cycle in crates. This will allow us to merge the new libproc_macro_tokens into libproc_macro. r? @alexcrichton
Separate the plugin code from non-plugin code to break a potential cycle in crates.
This will allow us to merge the new libproc_macro_tokens into libproc_macro.
r? @alexcrichton