rust/compiler/rustc_resolve/src/lib.rs, branch 1.50.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.50.02020-12-12T22:04:59+00:00Resolve enum field visibility correctly2020-12-12T22:04:59+00:00Camelidcamelidcamel@gmail.com2020-12-12T03:52:51+00:00urn:sha1:5ce3f4c16636b261a8ce9ddfbbb30896338b9e37
Previously, this code treated enum fields' visibility as if they were
struct fields. However, that's not correct because the visibility of a
struct field with `ast::VisibilityKind::Inherited` is private to the
module it's defined in, whereas the visibility of an *enum* field with
`ast::VisibilityKind::Inherited` is the visibility of the enum it
belongs to.
const_generics: assert resolve hack causes an error2020-11-20T22:29:54+00:00Bastian Kauschkebastian_kauschke@hotmail.de2020-11-20T16:03:12+00:00urn:sha1:34ea5d02ddaacfedd2d60460bf080b988b941d94rustc_resolve: Make `macro_rules` scope chain compression lazy2020-11-13T21:35:56+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2020-11-13T21:05:05+00:00urn:sha1:ac4c1f58b9fe1b4182b8af598751afd88caa5db5Auto merge of #78826 - petrochenkov:mrscopes2, r=eddyb2020-11-13T05:40:37+00:00borsbors@rust-lang.org2020-11-13T05:40:37+00:00urn:sha1:a38f8fb674e6a0a6fc358655c6ce6069235f621a
resolve: Collapse `macro_rules` scope chains on the fly
Otherwise they grow too long and you have to endlessly walk through them when resolving macros or imports.
Addresses https://rust-lang.zulipchat.com/#narrow/stream/247081-t-compiler.2Fperformance/topic/Slow.20Builtin.20Derives/near/215750815
rustc_resolve: Use `#![feature(format_args_capture)]`2020-11-07T22:38:11+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2020-11-07T22:38:11+00:00urn:sha1:907b87fafa249943db8af820d763d0255487264aresolve: Collapse `macro_rules` scope chains on the fly2020-11-06T23:18:29+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2020-11-06T13:11:21+00:00urn:sha1:922107919dfcd455f8957aef16a1b3e30db8fc44Fix even more clippy warnings2020-10-30T14:13:39+00:00Joshua Nelsonjyn514@gmail.com2020-10-27T01:02:48+00:00urn:sha1:57c6ed0c07aaea9c89a192e54b3274464ebe6fbf[resolve] Use `unwrap_or_else` instead of `unwrap_or` in a hot path2020-10-29T01:53:25+00:00Wesley Wiserwwiser@gmail.com2020-10-28T12:53:55+00:00urn:sha1:1c1c591c81a6fba8199355066a4b4ca00df659b2
This improves the performance of the `resolve_crate` function by 30% for
a very large single file crate with auto-generated C bindings.
Auto merge of #78134 - bugadani:arena-nodrop, r=lcnr2020-10-22T07:05:21+00:00borsbors@rust-lang.org2020-10-22T07:05:21+00:00urn:sha1:6b9fbf212a06944ff23325d2d63215805dc3c6c3
Use `DroplessArena` where we know the type doesn't need drop
This PR uses a single `DroplessArena` in resolve instead of three separate `TypedArena`s.
`DroplessArena` checks that the type indeed doesn't need drop, so in case the types change, this will result in visible failures.
Resolve: Use dropless arena for types that don't need drop2020-10-20T08:37:56+00:00Dániel Bugabugadani@gmail.com2020-10-20T08:37:56+00:00urn:sha1:d07ce65d56d527273a2a80862c8a69d0dbc88906