Skip to content

Enforce fatal error if an include fails #18

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

Closed
wants to merge 9 commits into from
Closed

Conversation

mlabbe
Copy link

@mlabbe mlabbe commented May 6, 2024

This requires pull request on treasure-map to be merged bluebrown/treasure-map#1

This could be made into a cli option, but I would highly recommend fatal error by default.

This requires pull request on treasure-map to be merged
bluebrown/treasure-map#1
@mlabbe mlabbe mentioned this pull request May 6, 2024
@bluebrown
Copy link
Owner

Hi thanks for the PR.

This doesnt seem to be ready to be merged mas its chainging alot of things that are specific to your fork.

@mlabbe
Copy link
Author

mlabbe commented May 7, 2024

Sorry for the confusion. I am surprised to see that the 5 commits I added 2 hours ago were added to the PR, just because I am working from the main branch.

You would want to just cherry pick this trivial change, and not the rest of my opinionated commits, which are not meant to be merged:

aa1d432

It effectively passes true to textfunc.MapClosure.

mlabbe added 3 commits May 30, 2024 10:45
Preserves build edge specification when using -o
makes it possible to use this with ninja build
@bluebrown bluebrown closed this Jun 1, 2024
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