aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/tests
Commit message (Collapse)AuthorAgeFilesLines
...
* Check for dyn impls in method resolutionLukas Wirth2021-02-081-0/+22
|
* Handle box with allocatorThiébaud Weksteen2021-01-221-0/+24
| | | | | | | | In 1.49.0, the definition of Box was modified to support an optional Allocator[1]. Adapt the parsing of the `box` keyword to supply the expected number of parameters to the constructor. [1] https://github.com/rust-lang/rust/commit/f288cd2e179f600fa00c2a407206a12f6c5a91e0
* Render Fn* trait objects and impl types as rust doesLukas Wirth2021-01-132-4/+19
|
* Proper handling $crate Take 2Edwin Cheng2021-01-071-0/+31
|
* Revert "Proper handling $crate and local_inner_macros"Jonas Schievink2021-01-031-31/+0
|
* Fixed nested eager macro bugEdwin Cheng2021-01-031-0/+46
|
* Merge #7133bors[bot]2021-01-021-0/+31
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | 7133: Proper handling $crate and local_inner_macros r=jonas-schievink a=edwin0cheng This PR introduces `HygineFrames` to store the macro definition/call site hierarchy in hyginee and when resolving `local_inner_macros` and `$crate`, we use the token to look up the corresponding frame and return the correct value. See also: https://rustc-dev-guide.rust-lang.org/macro-expansion.html#hygiene-and-hierarchies fixe #6890 and #6788 r? @jonas-schievink Co-authored-by: Edwin Cheng <[email protected]>
| * Introduce HygieneFrames for proper token hygineeEdwin Cheng2021-01-021-0/+31
| |
* | Merge #7134bors[bot]2021-01-021-0/+18
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7134: Fix infer error of macro invocation in array expr r=edwin0cheng a=edwin0cheng Fixed following infer error: ```rust macro_rules! bar { () => {0u32} } fn test() { let a = [bar!()]; // a : [unknown] } ``` bors r+ Co-authored-by: Edwin Cheng <[email protected]>
| * | Fix infer error of macro invocation in array exprEdwin Cheng2021-01-021-0/+18
| |/
* | Add ConstParams to the ide layerLukas Wirth2021-01-011-1/+0
| |
* | Add ConstParams to the HIRLukas Wirth2021-01-011-0/+17
|/
* Implement const block inferenceLukas Wirth2020-12-231-4/+9
|
* Implement const pat inferenceLukas Wirth2020-12-231-0/+30
|
* Make macro def krate mandatoryJonas Schievink2020-12-151-0/+6
| | | | Refactors builtin derive support to go through proper name resolution
* Move to upstream `macro_rules!` modelJonas Schievink2020-12-151-1/+0
|
* Add regression testEdwin Cheng2020-12-151-0/+24
|
* Add test for #6852Florian Diebold2020-12-131-0/+37
|
* Infer labeled blocksLukas Wirth2020-12-111-0/+56
|
* Upgrade ChalkFlorian Diebold2020-12-071-0/+43
| | | | | | | Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging. Fixes #6628.
* Use correct, full substs for self type in implFlorian Diebold2020-12-041-0/+19
| | | | | | | | Without arbitrary self types, the self type could never refer to the method type parameters, so this wasn't a problem; but with arbitrary self types, it can. This fixes the crash from #6668; but it doesn't make method resolution work for these methods.
* Properly infer tuple struct patterns when encountering ellipsisLukas Wirth2020-11-241-0/+48
|
* Properly infer tuple patterns when encountering ellipsisLukas Wirth2020-11-241-0/+47
|
* binary operator overload type inference: add test markRoland Ruckerbauer2020-10-141-0/+3
|
* Implement binary operator overloading type inferenceRoland Ruckerbauer2020-10-131-0/+86
|
* Use Ty::apply instead of simple and fix method resolution.Charles Lew2020-09-161-3/+1
|
* Add a test.Charles Lew2020-09-161-0/+38
|
* Merge #5971bors[bot]2020-09-132-18/+67
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5971: Implement async blocks r=flodiebold a=oxalica Fix #4018 @flodiebold already gave a generic guide in the issue. Here's some concern about implementation detail: - Chalk doesn't support generator type yet. - Adding generator type as a brand new type (ctor) can be complex and need to *re-introduced* builtin impls. (Like how we implement closures before native closure support of chalk, which is already removed in #5401 ) - The output type of async block should be known after type inference of the whole body. - We cannot directly get the type from source like return-positon-impl-trait. But we still need to provide trait bounds when chalk asking for `opaque_ty_data`. - During the inference, the output type of async block can be temporary unknown and participate the later inference. `let a = async { None }; let _: i32 = a.await.unwrap();` So in this PR, the type of async blocks is inferred as an opaque type parameterized by the `Future::Output` type it should be, like what we do with closure type. And it really works now. Well, I still have some questions: - The bounds `AsyncBlockImplType<T>: Future<Output = T>` is currently generated in `opaque_ty_data`. I'm not sure if we should put this code here. - Type of async block is now rendered as `impl Future<Output = OutputType>`. Do we need to special display to hint that it's a async block? Note that closure type has its special format, instead of `impl Fn(..) -> ..` or function type. Co-authored-by: oxalica <[email protected]>
| * Implement async blocksoxalica2020-09-102-18/+67
| |
* | Add box pattern testJonas Schievink2020-09-121-0/+25
|/
* Switch to expect_test from crates.ioAleksey Kladov2020-08-218-8/+8
|
* Rename ra_hir_ty -> hir_tyAleksey Kladov2020-08-139-0/+9980
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 04:32:01 +0000