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

use explicit wording for reading cvar value #1066

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

illwieckz
Copy link
Member

hOw DiD wE mIsSeD tHaT fOr So lOnG? 🤔️

Copy link
Contributor

@DolceTriade DolceTriade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this code works fine...

T operator*() const;

Means that * is overloaded to call Get()

@illwieckz
Copy link
Member Author

I think this code works fine...

T operator*() const;

Means that * is overloaded to call Get()

Ah… Well, I prefer explicit code. 🤷‍♀️️

@illwieckz illwieckz changed the title renderer: properly reading cvar value renderer: use explicit wording for reading cvar value Apr 6, 2024
@illwieckz
Copy link
Member Author

I renamed the commit renderer: use explicit wording for reading cvar value.

@slipher
Copy link
Member

slipher commented Apr 6, 2024

Should we nuke operator*?

@illwieckz
Copy link
Member Author

Should we nuke operator*?

I was going to ask the same. I don't want to have to guess the behavior of *ptr knowing it may differ according to the object type. It seems to just add extra mental load only to save on characters and allowing some kind of obfsucated code golf…

So if someone nukes it, I will approve…

@illwieckz illwieckz force-pushed the illwieckz/dpcvars branch 2 times, most recently from 694d041 to 904afab Compare April 21, 2024 15:30
@illwieckz
Copy link
Member Author

I added a commit to NUKE the confusing *cvar syntax, it was used nowhere else.

@illwieckz illwieckz changed the title renderer: use explicit wording for reading cvar value use explicit wording for reading cvar value Apr 21, 2024
@slipher
Copy link
Member

slipher commented Apr 21, 2024

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants