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

Update Value.spec.lua #165

Merged
merged 1 commit into from
Feb 1, 2023
Merged

Update Value.spec.lua #165

merged 1 commit into from
Feb 1, 2023

Conversation

Dionysusnu
Copy link
Contributor

No description provided.

@dphfox
Copy link
Owner

dphfox commented Jun 4, 2022

What's the motivation for this change?

@dphfox
Copy link
Owner

dphfox commented Feb 1, 2023

This change does not seem meaningful. Returning to it now I do not see any reason why this should be at all functionally different, and since no explanation has been given, I have no choice but to reject this PR.

@Dionysusnu
Copy link
Contributor Author

and since no explanation has been given, I have no choice but to reject this PR.

this was explained several times, but ignored on each. https://discord.com/channels/385151591524597761/895437663040077834/982713104574079037
https://discord.com/channels/385151591524597761/895437663040077834/980596243317272596

And a very simple look at the code would have shown it too. Passing a state directly into a Computed is not a valid way to use it. The test is clearly written to use a ForValues to test the garbage collection behaviour.

@dphfox
Copy link
Owner

dphfox commented Feb 1, 2023

and since no explanation has been given, I have no choice but to reject this PR.

this was explained several times, but ignored on each. https://discord.com/channels/385151591524597761/895437663040077834/982713104574079037
https://discord.com/channels/385151591524597761/895437663040077834/980596243317272596

And a very simple look at the code would have shown it too. Passing a state directly into a Computed is not a valid way to use it. The test is clearly written to use a ForValues to test the garbage collection behaviour.

Right so this is why I would have preferred the explanation to be here rather than buried in Discord chat. It is impossible to keep track of a pull requests history like that; while I was going through old PRs last night there was no explanation attached here and I had no idea of your intention whatsoever. Don't trust me to remember, please put the information where I (and perhaps more importantly, others) can find it.

I will look at this again later when I'm done with work.

@dphfox dphfox reopened this Feb 1, 2023
@dphfox dphfox added not ready - evaluating Currently gauging feedback and removed status: rejected labels Feb 1, 2023
@dphfox dphfox merged commit 14b5288 into dphfox:main Feb 1, 2023
@dphfox
Copy link
Owner

dphfox commented Feb 1, 2023

Apologies for the former lapse in judgement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not ready - evaluating Currently gauging feedback
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants