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

Documentation for trackUse/trackChange/trackAllow is very unclear #342

Open
ezyang opened this issue Dec 13, 2015 · 4 comments
Open

Documentation for trackUse/trackChange/trackAllow is very unclear #342

ezyang opened this issue Dec 13, 2015 · 4 comments
Labels

Comments

@ezyang
Copy link
Contributor

ezyang commented Dec 13, 2015

I was looking for a polymorphic version of want, and I accidentally tried to use trackUse (apparently, I'm supposed to use apply!)

@ndmitchell
Copy link
Owner

Yes, the track functions are still evolving, better docs is a must (and perhaps better semantics) - apply is what you are after.

@ezyang
Copy link
Contributor Author

ezyang commented Dec 13, 2015

Similarly, I think the Development.Shake.Rule would benefit from more guidance on how the pre-canned file operators can be reimplemented for custom rules. Or maybe it should have polymorphic versions of the operators.

@ndmitchell
Copy link
Owner

When you say precanned operators, do you mean things like %>, or things like traceUse, or both? Agreed, Shake.Rule should probably have some simple file rules as a demo.

@ezyang
Copy link
Contributor Author

ezyang commented Dec 18, 2015

Also things like "need".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants