Skip to content

Add --no-cache flag #1290

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

Merged
merged 4 commits into from
Sep 9, 2019
Merged

Add --no-cache flag #1290

merged 4 commits into from
Sep 9, 2019

Conversation

sjakobi
Copy link
Collaborator

@sjakobi sjakobi commented Sep 7, 2019

When enabled, we handle protected imports as if the semantic cache was
empty:

  • Protected imports are resolved again, downloaded or read from
    the filesystem as necessary.
  • Protected imports are β-normalized, not αβ-normalized.
  • Protected imports are checked against their SHA256 hashes,
    failing to resolve if they don't match.

Context:
#1275 (comment)

When enabled, we handle protected imports as if the semantic cache was
empty:
  * Protected imports are resolved again, downloaded or read from
    the filesystem as necessary.
  * Protected imports are β-normalized, not αβ-normalized.
  * Protected imports are checked against their SHA256 hashes,
    failing to resolve if they don't match.

Context:
#1275 (comment)
mCached <-
case _semanticCacheMode of
UseSemanticCache -> liftIO $ fetchFromSemanticCache semanticHash
IgnoreSemanticCache -> pure Nothing

case mCached of
Just bytesStrict -> do
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit further below we also writeToSemanticCache – IMHO it's not necessary to disable this, but we could.

@sjakobi sjakobi merged commit 37f819c into master Sep 9, 2019
@sjakobi sjakobi deleted the sjakobi/no-cache branch September 9, 2019 20:37
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