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

change Monoid#empty from nullary function to identity element itself #82

Closed
wants to merge 1 commit into from

Conversation

michaelficarra
Copy link
Contributor

😅

@puffnfresh
Copy link
Member

😐

@5outh
Copy link
Member

5outh commented Jan 22, 2015

I think I'm in favor of this, does it screw with anything? @puffnfresh

@puffnfresh
Copy link
Member

No preference. Can construct an argument either way.

@SimonRichardson
Copy link
Member

Question: should changes like this PR also fix all the other fantasy-land repos? By that I mean, if you create a PR like this, I'm expecting PRs for all the repos in fantasy-land which this breaks?

@5outh
Copy link
Member

5outh commented Jan 22, 2015

On second thought, changing the spec from how it was may cause other peoples' projects to no longer conform to it. If there's no preference either way, I think we should keep it the way it is.

@joneshf
Copy link
Member

joneshf commented Jan 22, 2015

We're semver'ing this thing, so we could just bump the version.

@5outh
Copy link
Member

5outh commented Jan 26, 2015

I think @SimonRichardson has a point, we should keep all of the fantasy-repositories up to date with the latest version, which is kind of unfortunate.

Should we take this to a vote or something?

@davidchambers davidchambers mentioned this pull request Jun 22, 2015
Closed
@davidchambers
Copy link
Member

This approach is incompatible with the current Id implementation:

// Monoid (value must also be a Monoid)
Id.prototype.empty = function() {
    return new Id(this.value.empty ? this.value.empty() : this.value.constructor.empty());
};

@SimonRichardson
Copy link
Member

Can we close this, it doesn't seem to over any value and consider it could break implementations I don't see the point. I hope you don't mind?

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.

6 participants