Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-13620] One-way constraint is not described in typeChecker.rst #56055

Open
LucianoPAlmeida opened this issue Sep 27, 2020 · 4 comments
Open

[SR-13620] One-way constraint is not described in typeChecker.rst #56055

LucianoPAlmeida opened this issue Sep 27, 2020 · 4 comments
Assignees
@hborla
Labels
compiler The Swift compiler in itself documentation improvement type checker Area → compiler: Semantic analysis

Comments

@LucianoPAlmeida
Copy link
Collaborator

Previous ID SR-13620
Radar None
Original Reporter @LucianoPAlmeida
Type Improvement
Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Improvement, Documentation, TypeChecker
Assignee @hborla
Priority Medium

md5: 7d645d435359e550226a021ca9594f22

Issue Description:

Trying to better understand some parts of the type checker and constraint system and couldn't find any mention of one-way constraint on docs/TypeChecker.rst, should we add a brief description there?
@LucianoPAlmeida
Copy link
Collaborator Author

cc @xedin @hborla

@typesanitizer
Copy link

This looks like the right place. �

@hborla
Copy link
Member

hborla commented Sep 28, 2020

Thanks for bringing this up! I definitely think TypeChecker.rst should include a description of unidirectional type inference and the solver's mechanism for it.

@LucianoPAlmeida for now, there's a good description in Doug's PR that added one-way constraints #25983 and there was some discussion about the motivation for adding one-way constraints on the forums here: https://forums.swift.org/t/function-builder-cannot-infer-generic-parameters-even-though-direct-call-to-buildblock-can/35886

@LucianoPAlmeida
Copy link
Collaborator Author

Have this described there would definitely help a lot. Thank you for all the references @hborla 🙂

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hborla hborla

Labels
compiler The Swift compiler in itself documentation improvement type checker Area → compiler: Semantic analysis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@typesanitizer @LucianoPAlmeida @hborla