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.

Sign up for GitHub

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

Jump to bottom

consider renaming [*.erasure] to [*.erase] #2516

Closed
zygoloid opened this issue Nov 26, 2018 · 2 comments
Closed

consider renaming [*.erasure] to [*.erase] #2516

zygoloid opened this issue Nov 26, 2018 · 2 comments

Comments

@zygoloid
Copy link
Member

We'd need to move [string.erase] out of the way first.

However, reserving [containername.erase] for a member named erase, and using a different name for the non-member form, seems preferable. Maybe [*.erase.nonmem] for the new ones?
@zygoloid zygoloid added the decision-required A decision of the editorial group (or the Project Editor) is required. label Nov 26, 2018
@zygoloid zygoloid mentioned this issue Nov 26, 2018
Merged
@jensmaurer
Copy link
Member

[*.erase.nonmem] seems a bit long...

@jensmaurer
Copy link
Member

jensmaurer commented Feb 22, 2019 •
edited by tkoeppe

Editorial meeting:

  • [string.erase] stays as-is.
  • Going for [*.string.nonmem] is worse than [*.erasure].
  • Net result: Do nothing.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Feb 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zygoloid @jensmaurer