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

Wheee, fix forecast problem in issue #4 #19

Merged
4 commits merged into from
Oct 26, 2010
Merged

Wheee, fix forecast problem in issue #4 #19

4 commits merged into from
Oct 26, 2010

Conversation

amalloy
Copy link
Collaborator

@amalloy amalloy commented Oct 26, 2010

Also, it seems to have added a merge commit, which ought to already be in your repo? I don't really know why it wants you to include that guy in the pull.

Maybe you'll disagree with my changes in the ->> area; if so just add unescape to the end of the original chain.
… had the effect of combining 3+ blank lines into only 2, but that's probably not such a bad thing.

For future reference, the script was:

find -name '*.clj' | xargs perl -i -e '$/="" ; while (<>) {s/\s*\n\s*([])}]+)/$1/s; print;}'
@amalloy
Copy link
Collaborator Author

amalloy commented Oct 26, 2010

Ummm, I don't understand why it's automatically adding everything I push into this pull request. I'd like 0e5d pulled, but it's not related to this issue at all; if I knew how I'd move it to another pull request.

@Raynes
Copy link
Owner

Raynes commented Oct 26, 2010

In the future, create new git branches for new features and bug fixes, and then add pull requests for that branch. Whenever you issue a pull request, any commits added to that branch are added to the pull request.

I didn't use reduce for in nil-comp because I didn't want it doing unnecessary computation. However, at the time I wrote that, I didn't know about the for's :while modifier. Take a look at the docs for for and see if you can use it rather than reduce. If I'm right, it should work perfectly.

Otherwise, excellent work!

This pull request was closed.
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.

None yet

2 participants