diff options
| author | Yuki Okushi <jtitor@2k36.org> | 2021-06-19 10:14:07 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-06-19 10:14:07 +0900 |
| commit | aa22799b365ca9b39267eab60a72914170ced369 (patch) | |
| tree | f3415d66ab041215ce747c4a50d2f502585d00e5 /library/std/src/sys/unix/process/process_unix.rs | |
| parent | ce1d5611a28468663e275078649e7ca6eef735a8 (diff) | |
| parent | 6288aada6de5c593a3d37bf51bbfda297d1b150b (diff) | |
| download | rust-aa22799b365ca9b39267eab60a72914170ced369.tar.gz rust-aa22799b365ca9b39267eab60a72914170ced369.zip | |
Rollup merge of #86136 - m-ou-se:proc-macro-open-close-span, r=m-ou-se
Stabilize span_open() and span_close(). This proposes to stabilize `Group::span_open()` and `Group::span_close()`. These are part of the `proc_macro_span` feature gate tracked in https://github.com/rust-lang/rust/issues/54725 Most of the features gated behind `proc_macro_span` are about source location information (file path, line and column information), expansion information (parent()), source_text(), etc. Those are not ready for stabilizaiton. However, getting the span of the `(` and `)` separately instead of only of the entire `(...)` can be very useful in proc macros, and doesn't seem blocked on anything that all the other parts of `proc_macro_span` are blocked on. So, this renames the feature gate for those two functions to `proc_macro_group_span` and stabilizes them.
Diffstat (limited to 'library/std/src/sys/unix/process/process_unix.rs')
0 files changed, 0 insertions, 0 deletions