aboutsummaryrefslogtreecommitdiff
path: root/crates/hir_ty/src/traits/chalk
Commit message (Collapse)AuthorAgeFilesLines
* Move things from `traits` module to `types` as wellFlorian Diebold2021-04-041-5/+3
|
* Move things in hir_ty into submodulesFlorian Diebold2021-04-041-5/+5
| | | | | - all the types that will be replaced by Chalk go to `types` - `TypeWalk` impls go to `walk`
* Introduce `GenericArg` like in ChalkFlorian Diebold2021-04-031-12/+27
| | | | | | | Plus some more adaptations to Substitution. Lots of `assert_ty_ref` that we should revisit when introducing lifetime/const parameters.
* Align InEnvironment with ChalkFlorian Diebold2021-03-211-4/+1
| | | | | | This in particular means storing a chalk_ir::Environment, not our TraitEnvironment. This makes InEnvironment not usable for Type, where we need to keep the full TraitEnvironment.
* Align Canonical more with Chalk's versionFlorian Diebold2021-03-211-25/+2
| | | | In particular, use chalk_ir::CanonicalVarKinds.
* Use QuantifiedWhereClause in generic_predicates as wellFlorian Diebold2021-03-211-1/+1
| | | | | Still far too much binder skipping going on; I find it hard to imagine this is all correct, but the tests pass.
* Introduce QuantifiedWhereClause and DynTy analogous to ChalkFlorian Diebold2021-03-211-42/+52
| | | | | This introduces a bunch of new binders in lots of places, which we have to be careful about, but we had to add them at some point.
* Turn Obligation into something similar to chalk_ir::DomainGoalFlorian Diebold2021-03-201-4/+6
| | | | This includes starting to make use of Chalk's `Cast` trait.
* Remove WhereClause::ErrorFlorian Diebold2021-03-201-6/+1
| | | | | Chalk doesn't have it, and judging from the removed code, it wasn't useful anyway.
* Rename GenericPredicate -> WhereClauseFlorian Diebold2021-03-201-14/+12
|
* Replace Projection variant in GenericPredicate with AliasEqLukas Wirth2021-03-191-33/+59
|
* Chalkify TraitRefFlorian Diebold2021-03-181-8/+7
|
* avoid converting types into themselves via .into() (clippy::useless-conversion)Matthias Krüger2021-03-171-1/+1
| | | | example: let x: String = String::from("hello world").into();
* Rename Substs -> SubstitutionFlorian Diebold2021-03-161-6/+9
|
* Use SmallVec for SubstsFlorian Diebold2021-03-151-3/+4
| | | | | Doesn't help as much as I hoped, but it helps a bit and I also did some refactorings that were necessary anyway.
* Don't use Substs for Ref/Raw/Array/SliceFlorian Diebold2021-03-141-17/+13
|
* Make Ty wrap TyKind in an ArcFlorian Diebold2021-03-141-1/+1
| | | | | | | | ... like it will be in Chalk. We still keep `interned_mut` and `into_inner` methods that will probably not exist with Chalk. This worsens performance slightly (5ginstr inference on RA), but doesn't include other simplifications we can do yet.
* More renamingFlorian Diebold2021-03-141-10/+8
|
* Use chalk_ir::FnSigFlorian Diebold2021-03-141-10/+9
|
* Rename some fields to their Chalk namesFlorian Diebold2021-03-141-11/+11
|
* Use chalk_ir::OpaqueTyIdFlorian Diebold2021-03-131-22/+6
|
* Use chalk_ir::PlaceholderIndexFlorian Diebold2021-03-131-19/+3
|
* Use chalk_ir::ClosureIdFlorian Diebold2021-03-131-8/+3
|
* Use chalk_ir::FnDefIdFlorian Diebold2021-03-132-4/+2
|
* Use chalk_ir::AssocTypeIdFlorian Diebold2021-03-132-38/+18
|
* Use chalk_ir::ForeignDefIdFlorian Diebold2021-03-132-23/+2
|
* Separate `Ty` and `TyKind` like in ChalkFlorian Diebold2021-03-131-45/+46
| | | | | Currently `Ty` just wraps `TyKind`, but this allows us to change most places to already use `intern` / `interned`.
* Use Chalk Environment more directlyFlorian Diebold2021-03-121-33/+5
|
* Use chalk_ir::AdtIdLukas Wirth2021-03-041-14/+2
|
* Use chalk_ir::MutabilityLukas Wirth2021-03-011-22/+6
|
* Introduce Ty::AliasLukas Wirth2021-03-011-10/+10
|
* Being Ty::InferenceVar closes to chalk equivalentLukas Wirth2021-03-011-22/+10
|
* Lift FnPointer into a structLukas Wirth2021-02-281-16/+12
|
* Remove Substs from Ty::ForeignTypeLukas Wirth2021-02-281-5/+4
|
* Turn Ty::Tuple variant into a tuple-variantLukas Wirth2021-02-281-2/+2
|
* Inline TypeCtor into TyLukas Wirth2021-02-281-104/+85
|
* Use chalk_ir::Scalar directlyLukas Wirth2021-02-281-60/+4
|
* Introduce TypeCtor::ScalarLukas Wirth2021-02-281-80/+60
|
* Update crateskjeremy2021-02-081-2/+3
| | | | Pulls in https://github.com/rust-lang/chalk/pull/682
* Upgrade ChalkFlorian Diebold2020-12-072-3/+26
| | | | | | | Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging. Fixes #6628.
* Remove more unreachable pubsAleksey Kladov2020-11-022-18/+18
|
* Deny unreachable-pubAleksey Kladov2020-11-021-27/+27
| | | | | | | | It's very useful when `pub` is equivalent to "this is crate's public API", let's enforce this! Ideally, we should enforce it for local `cargo test`, and only during CI, but that needs https://github.com/rust-lang/cargo/issues/5034.
* Upgrade Chalk to 0.36Florian Diebold2020-10-303-305/+166
| | | | Quite a few changes, because Chalk got rid of the `ApplicationTy` nesting.
* Get rid of FAKE_PLACEHOLDERFlorian Diebold2020-10-251-8/+9
| | | | | The lifetime placeholder can be replaced by the static lifetime, and for array sizes we should just be using a concrete const.
* Make unimplemented match variants explicitCasey Primozic2020-10-071-1/+2
|
* `todo!()` -> `unimplemented!() // FIXME` for CICasey Primozic2020-10-061-1/+1
|
* Bump chalk to use latest git to get fixCasey Primozic2020-10-061-0/+1
| | | | * Chalk very recently (like an hour ago) merged a fix that prevents rust analyzer from panicking. This allows it to be usable again for code that hits those situations. See #6134, #6145, Probably #6120
* Update chalk to 0.27 and adapt to chalk changes.Charles Lew2020-09-153-19/+62
|
* Merge #5971bors[bot]2020-09-131-0/+3
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-101-0/+3
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-30 23:00:56 +0000