Skip to content

Only allow one module per file#2126

Merged
garyb merged 1 commit into0.9from
single-module-files
May 15, 2016
Merged

Only allow one module per file#2126
garyb merged 1 commit into0.9from
single-module-files

Conversation

@garyb
Copy link
Copy Markdown
Member

@garyb garyb commented May 14, 2016

@paf31 I have a bit of time after all 😉

This is pretty straightforward, mostly updates to the docs tests to make them parse.

@hdgarrood
Copy link
Copy Markdown
Contributor

👍 lgtm

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.04%) to 55.9% when pulling 0e23de7 on single-module-files into 46f1687 on 0.9.

-> [(k, String)]
-> m [(k, Module)]
parseModulesFromFiles toFilePath input =
flip parU id $ map wrapError $ inParallel $ flip map input $ \(k, content) -> do
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Non-blocking: this can be simplified to flip parU wrapError . inParallel . flip map input.

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented May 14, 2016

👍 Thanks! I started this last night but stopped when I realized I had to change the examples 😄

@garyb garyb force-pushed the single-module-files branch from 0e23de7 to ef14768 Compare May 14, 2016 20:11
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.04%) to 55.9% when pulling ef14768 on single-module-files into 46f1687 on 0.9.

@paf31
Copy link
Copy Markdown
Contributor

paf31 commented May 15, 2016

👍 Looks good to merge.

@garyb garyb merged commit 7f29fad into 0.9 May 15, 2016
@kritzcreek kritzcreek mentioned this pull request May 15, 2016
@garyb garyb deleted the single-module-files branch May 15, 2016 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants