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

Add nre to stdlib #2818

Merged
merged 156 commits into from
Jun 11, 2015
Merged

Add nre to stdlib #2818

merged 156 commits into from
Jun 11, 2015

Conversation

flaviut
Copy link
Contributor

@flaviut flaviut commented May 26, 2015

Fixes #2511

@dom96
Copy link
Contributor

dom96 commented May 27, 2015

👍 for following Nimble conventions on hiding your implementation's private modules :)

@oprypin oprypin mentioned this pull request May 31, 2015
12 tasks
@dom96
Copy link
Contributor

dom96 commented Jun 4, 2015

Where are we with this?

@Araq
Copy link
Member

Araq commented Jun 5, 2015

@flaviut ping. ready for merging?

@flaviut
Copy link
Contributor Author

flaviut commented Jun 5, 2015

Yep, it is!
On Jun 5, 2015 7:52 AM, "Andreas Rumpf" [email protected] wrote:

@flaviut https://github.com/flaviut ping. ready for merging?


Reply to this email directly or view it on GitHub
#2818 (comment).

@Araq
Copy link
Member

Araq commented Jun 6, 2015

Well there is a conflict.

@dom96
Copy link
Contributor

dom96 commented Jun 8, 2015

155 commits? Just for a single new module?

@dom96
Copy link
Contributor

dom96 commented Jun 8, 2015

Wouldn't it be worth to squash these down?

@flaviut
Copy link
Contributor Author

flaviut commented Jun 8, 2015

This contains the complete commit history of nre. That means that people
can use or revert individual commits, along with any other of the other
advantages of source control.
On Jun 7, 2015 8:18 PM, "Dominik Picheta" [email protected] wrote:

155 commits? Just for a single new module?


Reply to this email directly or view it on GitHub
#2818 (comment).

@reactormonk
Copy link
Contributor

@dom96 What are more commits gonna cost you? A longer git bisect?

@dom96
Copy link
Contributor

dom96 commented Jun 8, 2015

Alright, fine.

Another thing: wouldn't it make more sense to keep re as it is. Won't rewriting it to use nre create the possibility for breakage?

@oprypin
Copy link
Contributor

oprypin commented Jun 8, 2015

I'd even say breakage is likely. I haven't properly tested that one.

Maybe backwards compatibility is worth more than correctness.

@Araq
Copy link
Member

Araq commented Jun 8, 2015

Well it's weird to deprecate and "fix" re at the same time. I say: Don't touch 're' if it's deprecated anyway.

This reverts commit dc60a51.
@flaviut
Copy link
Contributor Author

flaviut commented Jun 10, 2015

Sorry about the delay, I missed the email notification. I've reverted that commit.

Araq added a commit that referenced this pull request Jun 11, 2015
@Araq Araq merged commit d31fe76 into nim-lang:devel Jun 11, 2015
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.

Deprecate and replace 're' with 'nre'
5 participants