Skip to content

docker: build-box should set opam env#6

Closed
fdupress wants to merge 1 commit intoEasyCrypt:1.0from
fdupress:fix-build-box
Closed

docker: build-box should set opam env#6
fdupress wants to merge 1 commit intoEasyCrypt:1.0from
fdupress:fix-build-box

Conversation

@fdupress
Copy link
Copy Markdown
Member

No description provided.

@fdupress fdupress requested a review from strub March 15, 2018 16:47
@strub
Copy link
Copy Markdown
Member

strub commented Mar 16, 2018

Why? We're only installing stuffs in the switch, not using programs installed in the switch.

@fdupress
Copy link
Copy Markdown
Member Author

fdupress commented Mar 16, 2018 via email

@strub
Copy link
Copy Markdown
Member

strub commented Mar 16, 2018

Each docker RUN starts a new shell. So you won’t inherit this eval in the subsequent docker RUN.

@fdupress
Copy link
Copy Markdown
Member Author

Right. Sorry. The issue I was trying to get around with this is in fact due to something completely different: the fact that opam initialisation scripts are only run in login shells.

Closing this and trying to think of another way of dealing with this.

@fdupress fdupress closed this Mar 16, 2018
strub added a commit that referenced this pull request Apr 30, 2026
…hange)

Splits the existing TcCtt resolution logic into three named local helpers — strat_tvar_via_tvtc, strat_abs_via_decl, strat_infer_by_carrier — corresponding to catalog modes #5, #6, and #1/#2 in doc/typeclasses-inference.md.

Behavior is identical: same dispatch order, same failures, same pickup of [Tvar a]/[Tconstr p] cases, same parking of univar carriers. The refactor exists so Phase 3 can drop a By-args strategy in without disturbing the existing logic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants