- 02 4月, 2022 2 次提交
- 23 3月, 2022 1 次提交
-
-
由 b-naber 提交于
-
- 16 3月, 2022 1 次提交
-
-
由 mark 提交于
There are a few places were we have to construct it, though, and a few places that are more invasive to change. To do this, we create a constructor with a long obvious name.
-
- 15 2月, 2022 1 次提交
-
-
由 Nicholas Nethercote 提交于
Specifically, rename the `Const` struct as `ConstS` and re-introduce `Const` as this: ``` pub struct Const<'tcx>(&'tcx Interned<ConstS>); ``` This now matches `Ty` and `Predicate` more closely, including using pointer-based `eq` and `hash`. Notable changes: - `mk_const` now takes a `ConstS`. - `Const` was copy, despite being 48 bytes. Now `ConstS` is not, so need a we need separate arena for it, because we can't use the `Dropless` one any more. - Many `&'tcx Const<'tcx>`/`&Const<'tcx>` to `Const<'tcx>` changes - Many `ct.ty` to `ct.ty()` and `ct.val` to `ct.val()` changes. - Lots of tedious sigil fiddling.
-
- 25 9月, 2021 1 次提交
-
-
由 Aaron Hill 提交于
Currently, we use a relatively 'small' span for THIR expressions generated by an 'adjustment' (e.g. an autoderef, autoborrow, unsizing). As a result, if a borrow generated by an adustment ends up causing a borrowcheck error, for example: ```rust let mut my_var = String::new(); let my_ref = &my_var my_var.push('a'); my_ref; ``` then the span for the mutable borrow may end up referring to only the base expression (e.g. `my_var`), rather than the method call which triggered the mutable borrow (e.g. `my_var.push('a')`) Due to a quirk of the MIR borrowck implementation, this doesn't always get exposed in migration mode, but it does in many cases. This commit makes THIR building consistently use 'larger' spans for adjustment expressions The intent of this change it make it clearer to users when it's the specific way in which a variable is used (for example, in a method call) that produdes a borrowcheck error. For example, an error message claiming that a 'mutable borrow occurs here' might be confusing if it just points at a usage of a variable (e.g. `my_var`), when no `&mut` is in sight. Pointing at the entire expression should help to emphasize that the method call itself is responsible for the mutable borrow. In several cases, this makes the `#![feature(nll)]` diagnostic output match up exactly with the default (migration mode) output. As a result, several `.nll.stderr` files end up getting removed entirely.
-
- 09 9月, 2021 2 次提交
- 25 7月, 2021 1 次提交
-
-
由 Smitty 提交于
-
- 17 7月, 2021 1 次提交
-
-
由 Alex Huszagh 提交于
Implementation is based off fast-float-rust, with a few notable changes. - Some unsafe methods have been removed. - Safe methods with inherently unsafe functionality have been removed. - All unsafe functionality is documented and provably safe. - Extensive documentation has been added for simpler maintenance. - Inline annotations on internal routines has been removed. - Fixed Python errors in src/etc/test-float-parse/runtests.py. - Updated test-float-parse to be a library, to avoid missing rand dependency. - Added regression tests for #31109 and #31407 in core tests. - Added regression tests for #31109 and #31407 in ui tests. - Use the existing slice primitive to simplify shared dec2flt methods - Remove Miri ignores from dec2flt, due to faster parsing times. - resolves #85198 - resolves #85214 - resolves #85234 - fixes #31407 - fixes #31109 - fixes #53015 - resolves #68396 - closes https://github.com/aldanor/fast-float-rust/issues/15
-
- 22 5月, 2021 3 次提交
-
-
由 LeSeulArtichaut 提交于
-
由 LeSeulArtichaut 提交于
-
由 LeSeulArtichaut 提交于
-
- 19 5月, 2021 1 次提交
-
-
由 LeSeulArtichaut 提交于
-
- 12 3月, 2021 2 次提交
-
-
由 Oli Scherer 提交于
-
由 LeSeulArtichaut 提交于
-
- 10 3月, 2021 3 次提交
-
-
由 LeSeulArtichaut 提交于
-
由 LeSeulArtichaut 提交于
-
由 LeSeulArtichaut 提交于
-
- 18 11月, 2020 1 次提交
-
-
由 Aman Arora 提交于
This allows us to: - Handle precise Places captured by a closure directly in MIR. Handling captures in MIR is easier since we can rely on/ tweak PlaceBuilder to generate `mir::Place`s that resemble how we store captures (`hir::Place`). - Allows us to handle `let _ = x` case when feature `capture_disjoint_fields` is enabled directly in MIR. This is required to be done in MIR since patterns are desugared in MIR.
-
- 30 8月, 2020 1 次提交
-
-
由 mark 提交于
-
- 18 8月, 2020 1 次提交
-
-
由 Ujjwal Sharma 提交于
-
- 08 8月, 2020 1 次提交
-
-
由 Nicholas Nethercote 提交于
By moving `{known,used}_attrs` from `SessionGlobals` to `Session`. This means they are accessed via the `Session`, rather than via TLS. A few `Attr` methods and `librustc_ast` functions are now methods of `Session`. All of this required passing a `Session` to lots of functions that didn't already have one. Some of these functions also had arguments removed, because those arguments could be accessed directly via the `Session` argument. `contains_feature_attr()` was dead, and is removed. Some functions were moved from `librustc_ast` elsewhere because they now need to access `Session`, which isn't available in that crate. - `entry_point_type()` --> `librustc_builtin_macros` - `global_allocator_spans()` --> `librustc_metadata` - `is_proc_macro_attr()` --> `Session`
-
- 01 8月, 2020 1 次提交
-
-
由 Valentin Lazureanu 提交于
-
- 17 7月, 2020 1 次提交
-
-
由 Valentin Lazureanu 提交于
-
- 15 7月, 2020 3 次提交
-
-
由 Bastian Kauschke 提交于
-
由 Bastian Kauschke 提交于
-
由 Bastian Kauschke 提交于
-
- 29 6月, 2020 1 次提交
-
-
由 Dylan MacKenzie 提交于
-
- 24 4月, 2020 1 次提交
-
-
由 marmeladema 提交于
-
- 14 4月, 2020 1 次提交
-
-
由 Rustin-Liu 提交于
Rename fn_has_self_argument to fn_has_self_parameter Rename AssocItemKind::Method to AssocItemKind::Fn Refine has_no_input_arg Refine has_no_input_arg Revert has_no_input_arg Refine suggestion_descr Move as_def_kind into AssocKind Signed-off-by: NRustin-Liu <rustin.liu@gmail.com> Fix tidy check issue Signed-off-by: NRustin-Liu <rustin.liu@gmail.com>
-
- 02 4月, 2020 1 次提交
-
-
由 Mazdak Farrokhzad 提交于
-
- 30 3月, 2020 2 次提交
-
-
由 Mazdak Farrokhzad 提交于
-
由 Mazdak Farrokhzad 提交于
-
- 14 3月, 2020 1 次提交
-
-
由 Camille GILLOT 提交于
-
- 01 3月, 2020 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 21 2月, 2020 1 次提交
-
-
由 Mazdak Farrokhzad 提交于
-
- 20 2月, 2020 1 次提交
-
-
由 Dylan MacKenzie 提交于
-
- 16 2月, 2020 1 次提交
-
-
由 Camille GILLOT 提交于
-
- 14 1月, 2020 1 次提交
-
-
由 Ben Lewis 提交于
which requires a lot of unnecessary work to evaluate them further down the line.
-