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

[JS] Ref #15952 make toOpenArray works better #17001

Merged
merged 2 commits into from
Feb 10, 2021
Merged

Conversation

ringabout
Copy link
Member

@ringabout ringabout commented Feb 10, 2021

ref #15952 toOpenArray works better

@ringabout ringabout changed the title ref 15952 toOpenArray works in JS [JS] Ref 15952 make toOpenArray works better Feb 10, 2021
@ringabout ringabout changed the title [JS] Ref 15952 make toOpenArray works better [JS] Ref #15952 make toOpenArray works better Feb 10, 2021
@Araq Araq merged commit 9bd4f50 into nim-lang:devel Feb 10, 2021
@timotheecour
Copy link
Member

@Araq I added a label backport, just remove that new label if you disagree; I think that's easier than having to specify it in commit msg since it allows decision to be made/unmade after a PR is merged;
alternatively we can add 3 labels: backport_10, backport_20, backport_40 instead of backport

@Araq
Copy link
Member

Araq commented Feb 10, 2021

That's for @narimiran to decide as he is doing the backports.

@timotheecour
Copy link
Member

I've removed the backport label from this PR in light of #17006 (but the label itself is still useful IMO, to tag whether or not to backport PR's)

@Araq
Copy link
Member

Araq commented Feb 11, 2021

The label is useful but more useful would be "backport-1.2" etc.

Araq pushed a commit that referenced this pull request Feb 13, 2021
…17006)

* followup #17001: improve coverage for tests/openarray/topenarray.nim
narimiran pushed a commit that referenced this pull request Feb 18, 2021
* ref 15952 toOpenArray works in JS

* fix

(cherry picked from commit 9bd4f50)
narimiran pushed a commit that referenced this pull request Feb 18, 2021
…17006)

* followup #17001: improve coverage for tests/openarray/topenarray.nim

(cherry picked from commit 21e60b9)
@ringabout ringabout added the TODO: followup needed remove tag once fixed or tracked elsewhere label Feb 23, 2021
@timotheecour
Copy link
Member

The label is useful but more useful would be "backport-1.2" etc.

done, added those; only 1 need to be specified each time a backport is needed:
image

It looks like this PR was backported to 1.4.4, but we may need to revisit this for 1.4.6 because of #17006

note that toOpenArray with var param doesn't seem to actually work (ie source data isn't mutated), so it's not clear that #17001 actually improved things (it turned an error into a silent non-mutation)

@narimiran
Copy link
Member

Please continue to use commit messages containing [backport*] tag for stuff that needs to be backported.

These labels might be easier for y'all to tag, but harder for me to do backports. I'm removing them so we don't have stuff labeled, but without tag.

@timotheecour
Copy link
Member

Please continue to use commit messages containing [backport*] tag for stuff that needs to be backported.

the problem with commit messages is that it requires the decision to be made before the PR is merged; a label gives you more flexibility and hindsight since you can tag/untag after a PR is merged; in this case for example, it was discovered after the PR was merged that it causes an issue and probably shouldn't have been backported.

@Araq
Copy link
Member

Araq commented Feb 26, 2021

Sure but @narimiran is doing the work so we have to adapt. However, maybe there could be an official backport queue instead that lists commits to backport?

ardek66 pushed a commit to ardek66/Nim that referenced this pull request Mar 26, 2021
ardek66 pushed a commit to ardek66/Nim that referenced this pull request Mar 26, 2021
…ray.nim (nim-lang#17006)

* followup nim-lang#17001: improve coverage for tests/openarray/topenarray.nim
@metagn
Copy link
Collaborator

metagn commented Jan 4, 2024

What's the followup needed label for?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TODO: followup needed remove tag once fixed or tracked elsewhere
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants