rust/src/test/ui/codemap_tests, branch 1.66.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.66.12022-09-22T20:18:30+00:00Improve the help message for an invalid calling convention2022-09-22T20:18:30+00:00khyperia953151+khyperia@users.noreply.github.com2022-09-08T13:37:15+00:00urn:sha1:9a206a78eb1c4d73bd55432e02a5a29d871afb7cMention first and last macro in backtrace2022-07-19T03:07:54+00:00Michael Gouletmichael@errs.io2022-06-21T02:25:52+00:00urn:sha1:01b2379e4902658de68fcdca2a15b48fe4d57875Do not ICE when we have -Zunpretty=expand with invalid ABI2022-07-17T03:35:54+00:00Michael Gouletmichael@errs.io2022-07-17T03:35:54+00:00urn:sha1:26ecd44160f54395b3bd5558cc5352f49cb0a0baAuto merge of #97512 - scottmcm:add-coldcc, r=nagisa,lcnr2022-06-07T08:12:45+00:00borsbors@rust-lang.org2022-06-07T08:12:45+00:00urn:sha1:91cacb3faf987805675e39aca41859ec1fcabef3
Add support for emitting functions with `coldcc` to LLVM
The eventual goal is to try using this for things like the internal panicking stuff, to see whether it helps.
Mention filename in suggestion when it differs from primary span2022-06-01T16:52:03+00:00Esteban Küberesteban@kuber.com.ar2022-05-31T23:38:03+00:00urn:sha1:310b1a9062ea785116f85e889380600e4943de21Bless tests with the full list of conventions in the output2022-05-30T07:19:23+00:00Scott McMurrayscottmcm@users.noreply.github.com2022-05-29T08:29:42+00:00urn:sha1:055cfaf10d3223dff3c703a2dfff1ca714fd6742Add more *-unwind ABI variants2022-02-02T21:21:24+00:00Amanieu d'Antrasamanieu@gmail.com2022-02-01T17:53:45+00:00urn:sha1:547b4e601e797e7989f6fc9ebe921376c74bd1f0
The following *-unwind ABIs are now supported:
- "C-unwind"
- "cdecl-unwind"
- "stdcall-unwind"
- "fastcall-unwind"
- "vectorcall-unwind"
- "thiscall-unwind"
- "aapcs-unwind"
- "win64-unwind"
- "sysv64-unwind"
- "system-unwind"
Suggest using a temporary variable to fix borrowck errors2021-12-10T22:34:00+00:00Noah Levcamelidcamel@gmail.com2021-03-15T22:09:06+00:00urn:sha1:e27315268b10c9ef2f4c3d815dfc79f513327def
In Rust, nesting method calls with both require `&mut` access to `self`
produces a borrow-check error:
error[E0499]: cannot borrow `*self` as mutable more than once at a time
--> src/lib.rs:7:14
|
7 | self.foo(self.bar());
| ---------^^^^^^^^^^-
| | | |
| | | second mutable borrow occurs here
| | first borrow later used by call
| first mutable borrow occurs here
That's because Rust has a left-to-right evaluation order, and the method
receiver is passed first. Thus, the argument to the method cannot then
mutate `self`.
There's an easy solution to this error: just extract a local variable
for the inner argument:
let tmp = self.bar();
self.foo(tmp);
However, the error doesn't give any suggestion of how to solve the
problem. As a result, new users may assume that it's impossible to
express their code correctly and get stuck.
This commit adds a (non-structured) suggestion to extract a local
variable for the inner argument to solve the error. The suggestion uses
heuristics that eliminate most false positives, though there are a few
false negatives (cases where the suggestion should be emitted but is
not). Those other cases can be implemented in a future change.
Fix a format_args span to be expansion2021-10-29T22:13:15+00:00Cameron Steffencam.steffen94@gmail.com2021-10-21T14:01:16+00:00urn:sha1:4cfb7add771367757ee2dd26da4e29d333c93cb6Bless tests2021-10-15T07:36:58+00:00Cameron Steffencam.steffen94@gmail.com2021-10-14T18:28:28+00:00urn:sha1:90f4521cfdfc85fc04759cfba2f86a6acc096cb3