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

Invlet fix attempt #1352143-a: Don't initialize item charges in all cases. No comment. #3051

Conversation

Projects
None yet
2 participants
@atomicdryad
Copy link
Contributor

commented Sep 15, 2013

No description provided.

atomicdryad added some commits Sep 15, 2013

@kevingranade

This comment has been minimized.

Copy link
Member

commented Sep 17, 2013

I need:

  1. An outline of what this fixes so I can evaluate it.
  2. No commented out code.
@kevingranade

This comment has been minimized.

Copy link
Member

commented Sep 19, 2013

I can't make sense of this, I need an explanation of what it's supposed to do.

@atomicdryad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 20, 2013

item.charges / .invlets / .item_counter were not initialized in all cases prior to init() , this is a revert to pre-init behavior for those cases, in a hair pulling attempt to smash bug with thrice dammed invlets. item_counter getting clobbered in particular

@kevingranade

This comment has been minimized.

Copy link
Member

commented Sep 20, 2013

So you have no idea why, you're just pseudo reverting something that broke
it?

@atomicdryad

This comment has been minimized.

Copy link
Contributor Author

commented Sep 28, 2013

Yep. Since nobody wanted to test, and reverting to -exact- previous behavior is apparently verboten, close

@atomicdryad atomicdryad deleted the atomicdryad:invletsinvletsinvletsarghshootmeinthehead branch Sep 28, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.