lcnr
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee
    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee
  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # method calls We compute the `method_autoderef_steps` in a canonical query to prevent deref steps which don't matter from influencing candidate selection/inference. ## goal for opaque types Allow them in the autoderef steps and use `predicate_may_hold_opaque_types_jank` in `consider_probe`. Issues: - method selection is using `select_where_possible`. Need an alternative which treats opaque types jank as a hard error :heavy_check_mark: - could set a flag on the fulfillment context to treat opaque types as errors - unsatisfied predicates get returned for diagnostics. going `_` does not implement `Trait` seems ass :shrug: - if `Autoderef` returns not-yet-defined opaque types, we want to prevent constraining them during method selection? :thinking_face: - keep track of the # of steps where we encountered opaques - if it's less than the final number of steps, just check that way - if it's more, continue jank in a probe and make sure the step still results in an unconstrained opaque - issue: selection may change the deref chain - alternative: instantiate steps which result in opaques. if the instantiate failed, the deref chain is no longer applicable. if the opaque type ended up constrained, we error - `query method_autoderef_steps` uses old solver canonicalization, does not track opaque types - switch to new solver canonical - how, need to move new solver canonical out of the trait solver. ## `OpaqueTypesHack` why ```rust trait Foo: Sized { fn method(self) {} } impl Foo for u32 {} trait Bar: Sized { fn method(self) {} } impl Bar for u32 {} fn recur() -> impl Foo { if false { // Selects `Foo` on stable, would be ambig recur().method(); } 1u32 } ``` ```rust use std::ops::Deref; trait Foo { fn method(&self) {} } impl Foo for u32 {} fn via_deref() -> impl Deref<Target = impl Foo> { if false { via_deref().method(); } Box::new(1u32) } ``` ```rust use std::ops::Deref; struct Foo; impl Foo { fn method(&self) {} } fn via_deref() -> impl Deref<Target = Foo> { // Currently errors on stable, but should not if false { via_deref().method(); } Box::new(Foo) } ``` ## not constraining opaque types why ```rust trait Trait { fn foo(&self); } impl<T> Trait for T { fn foo(&self) {} } fn recur() -> impl Sized { if false { // We first try to match `&self` to `?hidden_ty` // which would constrain the opaque type to // `&?unconstrained`. recur().foo(); } () } ``` ```rust trait Trait { fn foo(&&self); } impl<T> Trait for T { fn foo(&&self) {} } fn recur() -> impl Sized { if false { let x = &recur(); // We first try to match `&self` to `?hidden_ty` // which would constrain the opaque type to // `&?unconstrained`. x.foo(); } () } ``` we could restrict this requirement to opaques in the final deref chain. This would cause method selection to be unstable ```rust trait Trait { fn method(self); } struct Foo; impl Trait for &Foo { fn method(self) { println!("trait"); } } impl Foo { fn method(&self) { println!("inherent"); } } fn recur(b: bool) -> impl Sized { if b { let x = &recur(!b); // Given the self type `&?hidden_type`, we only // match the `Trait` impl which constrains // the hidden type to `Foo`. Repeated method // selection now uses the inherent method. x.method(); x.method(); } Foo } ``` ## paths are fun ```rust #![feature(type_alias_impl_trait)] trait Trait { fn take_me(self); } impl<T> Trait for T { fn take_me(self) {} } type Tait = impl Sized; #[define_opaque(Tait)] fn main() { <Tait>::take_me(1u32); } ``` ## what is in a `Canonical` we've got inputs and outputs. inputs contain - `TypingMode` - `ParamEnv` - `predefined_opaques_in_body` (only in the new trait solver) outputs contain - the `CanonicalVarValues` to map vars back to the input - `certainty` - used by `solve::Response`, `infer::canonical::QueryResponse` - ignored by `inspect::State`, `make_query_response_ignoring_pending_obligations` - `region_constraints` - used by `solve::Response`, `infer::canonical::QueryResponse` - ignored by `inspect::State`, `make_query_response_ignoring_pending_obligations` - `opaque_types` - used by `solve::Response`, `infer::canonical::QueryResponse` - ignored by `inspect::State`, `make_query_response_ignoring_pending_obligations` - optional arbitrary `data/value` - `Ty` in normalizaiton `type_op`s - implied bounds in `query implied_outlives_bounds` - added goals or impl args in `inspect::State` - or `normalization_nested_goals` in `solve::Response` ### Differences whether input contains `predefined_opaques_in_body` `solve::Certainty` with `Maybe(MaybeCause)` vs `canonical::Certainty` with just `Ambiguous` concepts of "state/`make_query_response_ignoring_pending_obligations`" don't care about the final result, just take a snapshot of the current state in a canonical query new opaque type definitions: currently ignored by `state`, feels odd to do so? state should track opaque types canonical results can either be applied, or instantiated: - applying happens immediately after calling the query, infallible, only possible once - instantiate does not eagerly constrain var_values and opaques ### How to impl - move `query method_autoderef_steps` to new solver query input, include opaques https://github.com/lcnr/rust/pull/new/canonical-rustc_type_ir - we now know which infer vars are opaque hidden types there - don't care about the query output yet - list of indices where the self type is an opaque - confirm candidate checks whether any of them have gotten constraint - if they are from a later autoderef step -> instantiate in probe - THAT'S MAJOR ASS ## so gamer! Passing `predefined_opaques_in_body` to `method_autoderef_steps`, tracking which steps are opaque types, and erroring if the opaque gets constrained is gamer. Problem: - we don't want to error if applying a candidate causes later steps of the deref chain to no longer be reachable - this means that if instantiating ## terminology - deref[-chain] steps: `Box<T> -> T` - method-receivers: - for `Box<T>`: `Box<T>`, `&Box<T>`, `&mut Box<T>`, (`Pin<&T>` jank), then - for `T`: `T`, `&T`, `&mut T` (`Pin<&T>` jank) - candidate sources: derived from deref steps - candidate: method-receiver + source pair - `consider_probe`: test whether a pick is applicable :3 - `ProbeResult::BadReturnType` should be part of `NoMatch` :3

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully