-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ParamEnv
docs
#123327
Update ParamEnv
docs
#123327
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank u
@bors r+ rollup |
…compiler-errors Update `ParamEnv` docs There is now a wealth of information in the dev guide about `ParamEnv` so we should explicitly link to it from the doc comments. I also added a caution against using `ParamEnv` and removed the comment about it being "suitable for type checking" as you should practically never use `ParamEnv::empty` for type checking r? `@compiler-errors`
…compiler-errors Update `ParamEnv` docs There is now a wealth of information in the dev guide about `ParamEnv` so we should explicitly link to it from the doc comments. I also added a caution against using `ParamEnv` and removed the comment about it being "suitable for type checking" as you should practically never use `ParamEnv::empty` for type checking r? ``@compiler-errors``
This comment has been minimized.
This comment has been minimized.
tragic, my day is ruined @bors r- r=me when fixed :3 |
Yes, that should be correct. |
@bors r=compiler-errors |
…compiler-errors Update `ParamEnv` docs There is now a wealth of information in the dev guide about `ParamEnv` so we should explicitly link to it from the doc comments. I also added a caution against using `ParamEnv` and removed the comment about it being "suitable for type checking" as you should practically never use `ParamEnv::empty` for type checking r? `@compiler-errors`
…kingjubilee Rollup of 3 pull requests Successful merges: - rust-lang#123320 (Fixup parsing of `rustc_never_type_options` attribute) - rust-lang#123323 (std::thread: set_name change for solaris/illumos.) - rust-lang#123327 (Update `ParamEnv` docs) r? `@ghost` `@rustbot` modify labels: rollup
☀️ Test successful - checks-actions |
Finished benchmarking commit (dd5e502): comparison URL. Overall result: ❌✅ regressions and improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesThis benchmark run did not return any relevant results for this metric. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 668.149s -> 669.168s (0.15%) |
There is now a wealth of information in the dev guide about
ParamEnv
so we should explicitly link to it from the doc comments. I also added a caution against usingParamEnv
and removed the comment about it being "suitable for type checking" as you should practically never useParamEnv::empty
for type checkingr? @compiler-errors