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

Introduce explicit copy #15330

Merged
merged 4 commits into from
Sep 16, 2020
Merged

Introduce explicit copy #15330

merged 4 commits into from
Sep 16, 2020

Conversation

cooldome
Copy link
Member

The way to manage the performance warning. Also makes performance predictable.

@juancarlospaco
Copy link
Collaborator

Should it be {.inline.} ?.

@cooldome
Copy link
Member Author

added inline

@Araq Araq merged commit a3e9cc5 into devel Sep 16, 2020
@Araq Araq deleted the explicit_copy branch September 16, 2020 15:26
@Clyybber
Copy link
Contributor

Clyybber commented Sep 16, 2020

Maybe this should warn when we do an eplicit but unneccessary copy?

I think a better idea is to not emit the warnings unless requested, as this solution could lead to library authors not using sink so that the API is nicer.

@Araq Araq restored the explicit_copy branch September 16, 2020 18:33
Araq added a commit that referenced this pull request Sep 16, 2020
Araq added a commit that referenced this pull request Sep 16, 2020
@narimiran narimiran deleted the explicit_copy branch September 18, 2020 12:05
mildred pushed a commit to mildred/Nim that referenced this pull request Jan 11, 2021
mildred pushed a commit to mildred/Nim that referenced this pull request Jan 11, 2021
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