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

remove shallowCopy for ARC/ORC #20070

Merged
merged 14 commits into from
Jul 26, 2022
Merged

remove shallowCopy for ARC/ORC #20070

merged 14 commits into from
Jul 26, 2022

Conversation

ringabout
Copy link
Member

@ringabout ringabout commented Jul 21, 2022

todo:

  • changelog

lib/system.nim Outdated Show resolved Hide resolved
lib/system.nim Outdated Show resolved Hide resolved
compiler/btrees.nim Outdated Show resolved Hide resolved
lib/system.nim Outdated Show resolved Hide resolved
@ringabout
Copy link
Member Author

Two important packages are affected. It seems to be easy to fix them.

@ringabout
Copy link
Member Author

Prs prepared for important packages:

c-blake/cligen#217
mratsim/Arraymancer#562

@ringabout
Copy link
Member Author

My two prs were merged, just needing to wait for their new release.

@Vindaar
Copy link
Contributor

Vindaar commented Jul 25, 2022

My two prs were merged, just needing to wait for their new release.

I just did an arraymancer PR to also run the CI under ORC. I decided to run it in release mode, so it doesn't take up too much CI time. Locally I only ran the code in debug mode.

Turns out, what is essentially this issue (I think):

#19374

is still alive and kicking and breaks the ORC (and ARC, checked now locally) release tests of arraymancer:

https://github.com/mratsim/Arraymancer/runs/7499159222?check_suite_focus=true#step:18:4781

@ringabout
Copy link
Member Author

ringabout commented Jul 25, 2022

Yeah, we don't have ORC CI for arraymancer. The actual packages affected by this PR is numericalnim.

@ringabout
Copy link
Member Author

I just did an arraymancer PR to also run the CI under ORC. I decided to run it in release mode, so it doesn't take up too much CI time. Locally I only ran the code in debug mode.

Turns out, what is essentially this issue (I think):

Yeah, the issue blocks defaults to Orc

@Vindaar
Copy link
Contributor

Vindaar commented Jul 25, 2022

I see. Is it worth it to push a new arraymancer tag before that issue is fixed then? Personally I'd rather wait until it's fixed, make sure the CI passes & then push a new tag.

@ringabout
Copy link
Member Author

ringabout commented Jul 25, 2022

Is it worth it to push a new arraymancer tag before that issue is fixed then? Personally I'd rather wait until it's fixed, make sure the CI passes & then push a new tag.

This is a seperate critical issue for ARC/ORC. I hope this PR can be merged as soon as possible(this week is better).

@Vindaar
Copy link
Contributor

Vindaar commented Jul 25, 2022

Fair enough, just tagged a new version.

@ringabout ringabout closed this Jul 25, 2022
@ringabout ringabout reopened this Jul 25, 2022
@ringabout ringabout closed this Jul 25, 2022
@ringabout ringabout reopened this Jul 25, 2022
@ringabout
Copy link
Member Author

It seems to be ready since Packages CI / macos-10.15 (batch: 2_3) (pull_request) pass the CI although Packages CI / macos-10.15 (batch: 2_3) (push) doesn't.

@ringabout ringabout closed this Jul 25, 2022
@ringabout ringabout reopened this Jul 25, 2022
@ringabout ringabout closed this Jul 26, 2022
@ringabout ringabout reopened this Jul 26, 2022
@ringabout ringabout requested a review from Araq July 26, 2022 06:08
@Araq Araq merged commit 4c46358 into devel Jul 26, 2022
@Araq Araq deleted the pr_shallow branch July 26, 2022 14:51
@github-actions
Copy link
Contributor

Thanks for your hard work on this PR!
The lines below are statistics of the Nim compiler built from 4c46358

Hint: mm: orc; threads: on; opt: speed; options: -d:release
163556 lines; 15.033s; 841.086MiB peakmem

@Menduist
Copy link
Contributor

Wouldn't it have been better to just make it pop a warning in A/ORC? (Or ideally make it work under ARC/ORC, like an alias to move, but that may not be possible)

@ringabout
Copy link
Member Author

Wouldn't it have been better to just make it pop a warning in A/ORC? (Or ideally make it work under ARC/ORC, like an alias to move, but that may not be possible)

shallowCopy actually breaks code in ARC/ORC, here is a testcase => #20015 And it cannot be an alias for move because of different semantics.

make it pop a warning in A/ORC

See also discussions from #20025

FedericoCeratto pushed a commit to FedericoCeratto/Nim that referenced this pull request Jul 30, 2022
* remove shallowCopy for ARC/ORC

* use move

* fix

* more fixes

* typo

* Update lib/system.nim

* follow

* add nodestroy

* move

* copy string

* add a changelog entry

Co-authored-by: xflywind <43030857+xflywind@users.noreply.github.com>
Co-authored-by: Andreas Rumpf <rumpf_a@web.de>
@ringabout ringabout mentioned this pull request Sep 7, 2022
capocasa pushed a commit to capocasa/Nim that referenced this pull request Mar 31, 2023
* remove shallowCopy for ARC/ORC

* use move

* fix

* more fixes

* typo

* Update lib/system.nim

* follow

* add nodestroy

* move

* copy string

* add a changelog entry

Co-authored-by: xflywind <43030857+xflywind@users.noreply.github.com>
Co-authored-by: Andreas Rumpf <rumpf_a@web.de>
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.

4 participants