The Actix website.
Rust API guidelines
A easy-to-use command-line-parser.
Rust derive-based argument parsing optimized for code size
push eventrust-lang/rustc-dev-guide
commit sha a8b7e92c12f3d0f2fae55507a34a3fe329593069
Fix typo
push time in 4 hours
push eventrust-lang/rustc-dev-guide
commit sha 5f39b8131fc228cb70baa0e70a66b555e8f6fa6e
Add docs for x.py setup
push time in 4 days
PR merged rust-lang/rustc-dev-guide
Follow-up to https://github.com/rust-lang/rust/pull/76631
pr closed time in 4 days
pull request commentrust-lang/areweasyncyet.rs
minor documentation fix - missing space on line 37 of README.md
It's not a typo... the command works with and without the space.
comment created time in 6 days
push eventtshepang/mrh
commit sha 242eddb26263a3d7778cf96267db477e425d5426
bump version
push time in 6 days
push eventtshepang/mrh
commit sha a5081dc29e293340010d624414a78e5f31b86f4e
rm ugly annotation
commit sha 2ae1eda2a6b3440582848e62d55a0823e2cf80cc
one less direct dep
commit sha ec1a3823f6b49623404c02d42c375a89c4aa2c3b
bump dep: dirs
push time in 6 days
push eventtshepang/foo
push time in 15 days
pull request commentzonyitoo/rust-ini
Simpler code structure, moved everything to `lib.rs`
This should be bumped to v0.16.0 if it breaks code
comment created time in 16 days
push eventtshepang/seed-quickstart
commit sha 5a6fe59c754ce346cca915a41b4e7c23c925b0d0
missing word
push time in 16 days
Bare essentials to start a Seed app.
fork in 16 days
push eventtshepang/seed-rs.org
commit sha 3966926a1641fc0803b7e95ad381ed3133483f59
replace unusual usage
push time in 16 days
PR opened rust-lang/rust
Should been part of https://github.com/rust-lang/rust/pull/74163
pr created time in 17 days
push eventtshepang/rust
commit sha 7569cf98f93949880aae66fe843c90490f0f5120
Merge conflict fix: disambiguate f32 -> prim@f32 and u32 -> prim@u32
commit sha 1f2dd3b56aec4d8f97eb0b0552c166ef549d3316
Auto merge of #75903 - jyn514:lint-refactor, r=GuillaumeGomez Warn about unknown or renamed lints in rustdoc Fixes https://github.com/rust-lang/rust/issues/75884. This is best reviewed one commit at a time. r? @GuillaumeGomez Originally I tried to do a much broader refactoring that got rid of `init_lints` altogether. My reasoning is that now the lints aren't being run anymore (after https://github.com/rust-lang/rust/pull/73566), there's no need to ignore them explicitly. But it seems there are still some lints that aren't affected by setting `lint_mod` to a no-op: ``` deny(pub_use_of_private_extern_crate) deny(const_err) warn(unused_imports) ``` (there are possibly more, these are just the ones that failed in the rustdoc test suite). Some of these seem like we really should be warning about, but that's a much larger change and I don't propose to make it here. So for the time being, this just adds the `unknown_lints` and `renamed_or_removed_lints` passes to the list of lints rustdoc warns about.
commit sha 64c4bb0d2bac5f7810d7d0fa6ad846417b3ca60a
Auto merge of #5966 - 1c3t3a:1c3t3a-dev-5819-fix, r=Manishearth Corrects the float_equality_without_abs lint Fixes an issue in the `float_equality_without_abs` lint. The lint suggestion was configured in a way that it lints the whole error and not just the subtraction part. In the current configuration the lint would suggest to change the expression in a wrong way, e.g. ```rust let _ = (a - b) < f32::EPSILON; // before let _ = (a - b).abs(); // after ``` This was dicovered by @flip1995. (See discussion of PR #5952). Also the suggestion is now formatted via `utils::sugg`. changelog: none
commit sha 48717b6f3ce661d2a0d64f7bdfdfb5fd3484ee5b
Auto merge of #75912 - scottmcm:manuallydrop-vs-forget, r=Mark-Simulacrum Suggest `mem::forget` if `mem::ManuallyDrop::new` isn't used I think this communicates the intent more idiomatically, and is shorter anyway. Inspired because [it came up on URLO](https://users.rust-lang.org/t/validity-of-memory-area-after-std-forget/47730/7?u=scottmcm), and it turns out that std had done it too in one spot: 
commit sha 29399fad5f961f0e235d28ed2f4c68e7a1ae5062
Fix swapped stability attributes This fixes a regression introduced in https://github.com/rust-lang/rust/pull/74855.
commit sha aa40c028fcb20a47fb214fea2899ff9a8ae88840
Unstable Book: add links to tracking issues for FFI features
commit sha 2d8a3b9181f41d3af9b9f016c5d73b2553e344bf
Auto merge of #75944 - jumbatm:issue-75924-clashing-extern-decl-ice, r=spastorino Fix ICE on unwrap of unknown layout in ClashingExternDeclarations. Fixes #75924.
commit sha c8b240241a94a3a5badcbdcbe1b642a0dd440119
Avoid function-scoping global variables In 2e6f2e885506ee4, we added a main function to the publish_toolstate.py script. Unfortunately, we missed that the Python program implicitly declares global variables in that code, which means that adding a function changes variable scoping and breaks other code. This commit avoids introducing that function and adds a warning to future editors of the code.
commit sha 294c1160bb693a77ad2683321b9196352bd837dc
Improve docs for the `const` keyword
commit sha 30b7dac745b1555cd96f41977f7d24435cbe7fa2
Set ninja=true by default Ninja substantially improves LLVM build time. On a 96-way system, using Make took 248s, and using Ninja took 161s, a 35% improvement. We already require a variety of tools to build Rust. If someone wants to build without Ninja (for instance, to minimize the set of packages required to bootstrap a new target), they can easily set `ninja=false` in `config.toml`. Our defaults should help people build Rust (and LLVM) faster, to speed up development.
commit sha 181ce0e013453fcbe2cc493a37ea77d7cfe6b990
Disable ninja on macOS CI Should be re-enabled when we have a recipe for installing ninja on macOS.
commit sha 6149dffff959c0c338ef319b4cea2f49560041e7
Install ninja on CI builders Windows CI builds already install ninja. Install it in all the Docker-based builds as well.
commit sha bb39f3555c14275472386ffca637071e22714521
Provide a better diagnostic if ninja isn't installed Let people know that they can set ninja=false if they don't want to install ninja.
commit sha edc05da57d4ad5ab19b5ca64e80e359e487ab2d0
Fix the wrong use of `snippet_with_applicability` This includes a workaround of the issue #5822, the cause of this little mistake.
commit sha 45a83e97ccc70a99794346eb60c11e209c67ecba
Auto merge of #75898 - lcnr:variant-def-recovered, r=petrochenkov VariantDef: move `recovered` into `VariantFlags`
commit sha e45c59e922c4450b8ab136eac38a37000fca9254
Auto merge of #5968 - rail-rain:fix_use_snippet_with_applicability, r=flip1995 Fix the wrong use of `snippet_with_applicability` For the context, please see https://github.com/rust-lang/rust-clippy/issues/5822#issuecomment-680749728 and https://github.com/rust-lang/rust-clippy/issues/5822#issuecomment-680783381. --- changelog: none
commit sha 2eec2ecbdec1cae9b749e079a376540d9cc5e304
Rollup merge of #74730 - androm3da:fix_libstd_hexlinux_01, r=dtolnay Hexagon libstd: update type defs
commit sha 730449d22ad6d152f4f58719ef2f3c459984a361
Rollup merge of #75758 - bpangWR:master, r=Mark-Simulacrum Fixes for VxWorks r? @alexcrichton
commit sha a79f9af290ad69cd4fb32a3e1b5e610a21262717
Rollup merge of #75780 - matklad:unconfuseunpindocs, r=KodrAus Unconfuse Unpin docs a bit * Don't say that Unpin is used to prevent moves, because it is used to *allow* moves * Be more precise about kindedness of things, it is `Pin<Pointer<Data>>`, rather than just `Pin<Pointer>`.
commit sha 463fdf3e042c7429f2d85d2cdc042463d2cd7720
Rollup merge of #75806 - GuillaumeGomez:prevent-automatic-page-change-history, r=pickfire Prevent automatic page change when using history Fixes #75774.
push time in 17 days
Pull request review commentrust-lang/rustc-dev-guide
Document new way to not build LLVM
git worktree add -b my-feature ../rust2 master You can then use that rust2 folder as a separate workspace for modifying and building `rustc`! -## Building with system LLVM+## Skipping LLVM Build -By default, LLVM is built from source, and that can take significant amount of-time. An alternative is to use LLVM already installed on your computer.+By default, LLVM is built from source, and that takes significant amount of+time. One way to avoid that is to add this to `config.toml`: -This is specified in the `target` section of `config.toml`:+```toml+[llvm]+download-ci-llvm = true+```++Downloading LLVM from CI is still experimental though, and might not be+available on all platforms. Otherwise, we'd make it a default!
I was only referring to "Other, we'd make it a default". First sentence is all good.
comment created time in 17 days
Pull request review commentrust-lang/rustc-dev-guide
Document new way to not build LLVM
git worktree add -b my-feature ../rust2 master You can then use that rust2 folder as a separate workspace for modifying and building `rustc`! -## Building with system LLVM+## Skipping LLVM Build -By default, LLVM is built from source, and that can take significant amount of-time. An alternative is to use LLVM already installed on your computer.+By default, LLVM is built from source, and that takes significant amount of+time. One way to avoid that is to add this to `config.toml`: -This is specified in the `target` section of `config.toml`:+```toml+[llvm]+download-ci-llvm = true+```++Downloading LLVM from CI is still experimental though, and might not be+available on all platforms. Otherwise, we'd make it a default!
This does not feel like the right place to indicate planned policy/default, here referring to "we'd make it a default".
comment created time in 17 days
delete branch rust-lang/rustc-dev-guide
delete branch : LeSeulArtichaut-patch-1
delete time in 19 days
push eventLeSeulArtichaut/rustc-guide
commit sha 7579014ccc0d929657b589480cc73f0a4529474e
Update src/rustbot.md
push time in 19 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on useful `@rustbot` commands
+# Mastering @rustbot++`@rustbot` (also known as `triagebot`) is a utility robot that is mostly used to+allow any contributor to achieve certain tasks that would normally require GitHub+membership to the `rust-lang` organization. Its most interesting features for+contributors to `rustc` are isssue claiming and relabeling.++## Issue claiming++`@rustbot` exposes a command that allows anyone to assign an issue to themselves.+If you see an issue you want to work on, you can send the following message as a+comment on the issue at hand:++ @rustbot claim++If you are a member of the `rust-lang` organization, `@rustbot` will assign the+issue to you. Otherwise, `@rustbot` will assign itself as a placeholder and edit+the top comment to reflect the fact that the issue is now assigned to you.++If you want to unassign from an issue, `@rustbot` has a different command:++ @rustbot release-assignment++## Issue relabeling++Changing labels for an issue or PR is also normally reserved to members of the+organization. However, `@rustbot` allows you to relabel an issue yourself, only+with a few restrictions. This is mostly useful in two cases:++**Helping with issue triage**: Rust's issue tracker has more than 5,000 open+issues at the time of this writing, so labels are the most powerful tool that we+have to keep it as tidy as possible. You may not spend hours in the issue tracker+to triage issues, but if you open an issue, you should feel free to label it if+you are comfortable with doing it yourself.++**Updating the status of a PR**: we use "status labels" to reflect the status of+PRs. For example, if your PR has merge conflicts, it will automatically be assigned+the `S-waiting-on-author`, and reviewers might not review it until you rebase your+PR. Once you did rebase your branch, you should change the labels yourself to remove
PR. Once you do rebase your branch, you should change the labels yourself to remove
comment created time in 19 days
push eventLeSeulArtichaut/rustc-guide
commit sha 52691642a337c25bd4cbaafa3efe89be0b18fb36
Update src/rustbot.md
push time in 19 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on useful `@rustbot` commands
+# Mastering @rustbot++`@rustbot` (also known as `triagebot`) is a utility robot that is mostly used to+allow any contributor to achieve certain tasks that would normally require GitHub+membership to the `rust-lang` organization. Its most interesting features for+contributors to `rustc` are isssue claiming and relabeling.++## Issue claiming++`@rustbot` exposes a command that allows anyone to assign an issue to themselves.+If you see an issue you want to work on, you can send the following message as a+comment on the issue at hand:++ @rustbot claim++If you are a member of the `rust-lang` organization, `@rustbot` will assign the+issue to you. Otherwise, `@rustbot` will assign itself as a placeholder and edit+the top comment to reflect the fact that the issue is now assigned to you.++If you want to unassign from an issue, `@rustbot` has a different command:++ @rustbot release-assignment++## Issue relabeling++Changing labels for an issue or PR is also normally reserved to members of the+organization. However, `@rustdoc` allows you to relabel an issue yourself, only
organization. However, `@rustbot` allows you to relabel an issue yourself, only
comment created time in 19 days
push eventLeSeulArtichaut/rustc-guide
commit sha b19cdd46dc63efe2e23be09c148a9b9fd1b3f5e3
Update src/contributing.md Co-authored-by: Camelid <[email protected]>
push time in 19 days
push eventLeSeulArtichaut/rustc-guide
commit sha 0761d345b2bf0a0713629581b35cf4276a53c45c
Update src/contributing.md
push time in 19 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on useful `@rustbot` commands
labels to triage issues: * Red, **I**-prefixed labels indicate the **importance** of the issue. The [I-nominated][inom] label indicates that an issue has been nominated for- prioritizing at the next triage meeting.+ prioritizing at the next triage meeting. Similarely, the [I-prioritize][ipri]
prioritizing at the next triage meeting. Similarly, the [I-prioritize][ipri]
comment created time in 19 days
push eventrust-lang/rustc-dev-guide
commit sha ee99dea822d95e3bfef58b455e30a4080a044b09
Clean up 'Contributing to Rust - Pull Requests'
commit sha 6366c1dbaae299b04517541557889b4c14a20ccf
Apply suggestions from code review Co-authored-by: Joshua Nelson <[email protected]>
commit sha 150b915338bac3e6fcf903433c122e00cafdc153
Fix typo Co-authored-by: Tshepang Lekhonkhobe <[email protected]>
push time in 20 days
PR merged rust-lang/rustc-dev-guide
Also helps with #866.
pr closed time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Clean up 'Contributing to Rust - Pull Requests'
make a documentation change, add to the end of the pull request description, and [@rust-highfive][rust-highfive] will assign [@steveklabnik][steveklabnik] instead of a random person. This is entirely optional. +In addition to being reviewed by a human, pull requests are automatically tested+thanks to continuous integration (CI). Basically, every time you open and update+a pull request, CI builds the compiler and tests it against the+[compiler test suite][rctd], and also performs other tests such as checking that+your pull request is in compliance with Rust's style guidelines.++Running continuous integration tests allows PR authors to catch mistakes early+without going through a first review cycle, and also helps reviewers stay aware+of the status of a particular pull request.++Rust has plenty of CI capacity, and you should never have to worry about wasting+computational resources each time you push a change. It is also perfectly fine+(and even encouraged!) to use the CI to test your changes if it can help your+productivity. In particular, we don't recommend running the full `x.py test` suite locally,+since it takes a very long time to execute.+ After someone has reviewed your pull request, they will leave an annotation on the pull request with an `r+`. It will look something like this: @bors r+ This tells [@bors], our lovable integration bot, that your pull request has been approved. The PR then enters the [merge queue][merge-queue], where [@bors]-will run all the tests on every platform we support. If it all works out,+will run *all* the tests on *every* platform we support. If it all works out, [@bors] will merge your code into `master` and close the pull request. Depending on the scale of the change, you may see a slightly different form of `r+`: @bors r+ rollup -The additional `rollup` tells [@bors] that this change is eligible for to be-"rolled up". Changes that are rolled up are tested and merged at the same time, to+The additional `rollup` tells [@bors] that this change should always be "rolled up".+Changes that are rolled up are tested and merged alongside other PRs, to speed the process up. Typically only small changes that are expected not to conflict-with one another are rolled up.+with one another are marked as "always roll up". [rust-highfive]: https://github.com/rust-highfive [steveklabnik]: https://github.com/steveklabnik [@bors]: https://github.com/bors [merge-queue]: https://buildbot2.rust-lang.org/homu/queue/rust -Speaking of tests, Rust has a comprehensive test suite. More information about-it can be found [here][rctd].+### Opening a PR++You are now ready to file a pull request? Great! Here are a few points you+should be aware of.++All pull requests should be filed against the `master` branch, except in very+particular scenarios. Unless you know for sure that you should target another+branch, `master` will be the right choice (it's also the default).++Make sure your pull request is in compliance with Rust's style guidelines by running++ $ ./x.py test tidy --bless++We recommand to make this check before every pull request (and every new commit
We recommend to make this check before every pull request (and every new commit
comment created time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Clean up 'Contributing to Rust - Pull Requests'
make a documentation change, add to the end of the pull request description, and [@rust-highfive][rust-highfive] will assign [@steveklabnik][steveklabnik] instead of a random person. This is entirely optional. +In addition to being reviewed by a human, pull requests are automatically tested+thanks to continuous integration (CI). Basically, every time you open and update+a pull request, CI builds the compiler and tests it against the
The inconsistency bothered me
comment created time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Clean up 'Contributing to Rust - Pull Requests'
make a documentation change, add to the end of the pull request description, and [@rust-highfive][rust-highfive] will assign [@steveklabnik][steveklabnik] instead of a random person. This is entirely optional. +In addition to being reviewed by a human, pull requests are automatically tested+thanks to continuous integration (CI). Basically, every time you open and update+a pull request, CI builds the compiler and tests it against the
This avoids having to decide between pull request and Pull Request
comment created time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Clean up 'Contributing to Rust - Pull Requests'
make a documentation change, add to the end of the pull request description, and [@rust-highfive][rust-highfive] will assign [@steveklabnik][steveklabnik] instead of a random person. This is entirely optional. +In addition to being reviewed by a human, pull requests are automatically tested+thanks to continuous integration (CI). Basically, every time you open and update+a pull request, CI builds the compiler and tests it against the
a PR, CI builds the compiler and tests it against the
comment created time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on all the identifiers used through `rustc`
+# Identifiers in the Compiler++If you have read the few previous chapters, you now know that the `rustc` uses+many different intermediate representations to perform different kinds of analysis.
many different intermediate representations to perform different kinds of analyses.
comment created time in 20 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on all the identifiers used through `rustc`
+# Identifiers in the Compiler++If you have read the few previous chapters, you now know that the `rustc` uses
If you have read the few previous chapters, you now know that `rustc` uses
comment created time in 20 days
push eventrust-lang/rustc-dev-guide
commit sha 7d544181379af99e80c7e48647f7a30acc90dd8c
Document how to promote a target from cross-compiled to hosted
commit sha 987b5ef0085c3ac490ad84a99f236351603b7537
Update src/building/new-target.md
commit sha 683cbdda74559b7d3cdc79ede2b4305f876a1102
Fix nit
push time in 21 days
PR merged rust-lang/rustc-dev-guide
I don't know anything about how this works, just enough to link to more resources. r? @pietroalbini - and if you have more suggestions of docs to add, please let me know!
pr closed time in 21 days
pull request commentrust-lang/rustc-dev-guide
Document speculative crate loading
maybe we should bring in bors
comment created time in 21 days
pull request commentrust-lang/rustc-dev-guide
Document how to promote a target from cross-compiled to hosted
I see no need to wait... this is useful enough, and I did learn just by reading this PR. We can indeed always update it later.
comment created time in 21 days
push eventjyn514/rustc-dev-guide
commit sha b15f73261e2b87a2521282005d2da1cebf8c371d
Update src/building/new-target.md
push time in 21 days
push eventrust-lang/rustc-dev-guide
commit sha 13c18fccbeb61d0580be8e1c9cc13d0b9a5efe0b
Fix typo
push time in 21 days
PR merged rust-lang/rustc-dev-guide
r? @nico-abram
pr closed time in 21 days
push eventrust-lang/rustc-dev-guide
commit sha 677a95f264c22a9750d46d59ef1c4b74819080b3
Update error codes to match the current implementation - All codes are in one crate, `rustc_error_codes` - Extended descriptions are loaded using `include_str!` - Give an example of a PR adding an error code
push time in 23 days
PR merged rust-lang/rustc-dev-guide
- All codes are in one crate,
rustc_error_codes - Extended descriptions are loaded using
include_str!
I wrote this just by looking at the code, not by talking with anyone about it, so this might not be perfectly accurate. Follow-up to https://github.com/rust-lang/rustc-dev-guide/pull/838#discussion_r479810627.
r? @mark-i-m
pr closed time in 23 days
push eventjyn514/rustc-dev-guide
commit sha 928cd7865a6e617e74d5316c835c30717a54f8a0
Update src/building/how-to-build-and-run.md
push time in 24 days
Pull request review commentrust-lang/rustc-dev-guide
Link to 'prerequisites' immediately
be hacking on `rustc`, you'll want to tweak the configuration of the compiler. The default configuration is oriented towards running the compiler as a user, not a developer. +For instructions on how to install python and other prerequisites,
For instructions on how to install Python and other prerequisites,
comment created time in 24 days
push eventrust-lang/rustc-dev-guide
commit sha bb4695345ed432382f20e7ee1023754fa04a215c
Rename src/rustc to compiler/rustc
push time in 24 days
push eventrust-lang/rustc-dev-guide
commit sha af533030a27168df357398ed47d605ee54441f06
Fix dep-graph-caller-callee test location
push time in a month
PR merged rust-lang/rustc-dev-guide
pr closed time in a month
push eventrust-lang/rustc-dev-guide
commit sha b737f79192fab31fe630d067ee4faba51494ba4e
Adds documentation to cover spanview output Documents the feature introduced in #76074.
push time in a month
PR merged rust-lang/rustc-dev-guide
Documents the feature introduced in https://github.com/rust-lang/rust/pull/76074.
r? @tmandry FYI @wesleywiser
pr closed time in a month
push eventrust-lang/rustc-dev-guide
commit sha 2924b6962d5c548a9e37f8e768dad68047215a0b
Use fewer stages in bootstrapping docs After https://github.com/rust-lang/rust/pull/73964, they're redundant.
push time in a month
PR merged rust-lang/rustc-dev-guide
After https://github.com/rust-lang/rust/pull/73964, they're redundant.
pr closed time in a month
push eventrust-lang/rustc-dev-guide
commit sha 9ab50113c21055d7a6dda8f010f5b9d087e32ed1
Fix misguided suggestions in config.toml - `verbose-tests` is for debugging the test harness, not the tests themselves. See also https://github.com/rust-lang/rust/pull/76141 - `codegen-units` defaults to `256` whenever `incremental = true`. So there's no need to explicitly set it to `0` if we already recommend incremental. See also https://github.com/rust-lang/rustc-dev-guide/pull/795#discussion_r479762977.
push time in a month
PR merged rust-lang/rustc-dev-guide
verbose-testsis for debugging the test harness, not the tests themselves. See also https://github.com/rust-lang/rust/pull/76141codegen-unitsdefaults to256wheneverincremental = true. So there's no need to explicitly set it to0if we already recommend incremental. See also https://github.com/rust-lang/rustc-dev-guide/pull/795#discussion_r479762977.
r? @eddyb
pr closed time in a month
issue closedrust-lang/rustc-dev-guide
fix obsolete reference to diagnostic.rs
There is no file named compiler/rustc_typeck/src/diagnostics.rs. I ran into this while trying to add a new error code: all diagnostics are now in compiler/rustc_error_codes/src/error_codes.rs, which has one very long register_diagnostics!, and nowhere else adds error codes. register_long_diagnostics! also seems to no longer exist, instead that file uses include_str!("./error_codes/E0XXX.md").
Originally posted by @jyn514 in https://github.com/rust-lang/rustc-dev-guide/pull/838#r479810627
closed time in a month
tshepang
push eventrust-lang/rustc-dev-guide
commit sha 9bb3872dc742e1d403841460feba53d62310330a
fix links and names after compiler mv to compiler/
commit sha b259473dd18c5ac7c9ec451d4e083441dc0dafc8
fix line lengths
commit sha 4cb43d81603dab7f65448029b20d81226dccdb9b
fix typos
commit sha 45a153500720933a7445ff98cd0b093958a4b177
Typo Co-authored-by: Joshua Nelson <[email protected]>
push time in a month
issue openedrust-lang/rustc-dev-guide
fix obsolete reference to diagnostic.rs
There is no file named compiler/rustc_typeck/src/diagnostics.rs. I ran into this while trying to add a new error code: all diagnostics are now in compiler/rustc_error_codes/src/error_codes.rs, which has one very long register_diagnostics!, and nowhere else adds error codes. register_long_diagnostics! also seems to no longer exist, instead that file uses include_str!("./error_codes/E0XXX.md").
Originally posted by @jyn514 in https://github.com/rust-lang/rustc-dev-guide/pull/838#r479810627
created time in a month
push eventtshepang/blog
commit sha 1b8066b2efa148532bcf2d6a4b5d8d50a3f255e5
make more readable
commit sha d4ddf494986d19b85ef445206cd6ac292177fec3
more accurate
commit sha dcdf994627e0d3ae55c92a52f932e0edbd455eae
make more clear
push time in a month
push eventtshepang/tshepang.github.com
commit sha ed95b8ab0c6867cd36f2cec3881d93e09a8cd2c4
build
push time in a month