-
Notifications
You must be signed in to change notification settings - Fork 7
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
Random comments #226
Closed
Closed
Random comments #226
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
bjorn3
reviewed
Feb 5, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
vext01
reviewed
Feb 8, 2021
ptersilie
reviewed
Feb 8, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
ptersilie
reviewed
Feb 19, 2021
bors bot
added a commit
that referenced
this pull request
Feb 22, 2021
253: Address more comments from #226. r=ltratt a=ptersilie Co-authored-by: Lukas Diekmann <[email protected]>
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
ptersilie
reviewed
Feb 22, 2021
Is there anything not yet fixed? |
@ptersilie Any thoughts on @bjorn3's question? |
Resolved discussions. |
Sorry, wrong button. |
Can we close this? |
I believe this is now completed, so I'm closing it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Do not merge this ever, under any circumstances -- this is not a normal PR!!!
This is not a PR intended for merge: it's a complete repo code review. Inevitably it's shallow, but it's still thrown up some interesting things. Overall, I'm pretty happy with the code, but we can always improve things :)
There's a mix of things in here. Sometimes I've rephrased a comment; sometimes I've asked a question; less often I have a code change suggestion. So sometimes you can probably just copy an edited thing into your own PR; but sometimes we'll have to have a debate here to decide the way forwards.
What I suggest is that @ptersilie and @vext01 go through each bit of the diff and we use the nomal GitHub comments to decide on things. Then we can open up one or more PRs that address the valid comments in this PR.
Some general comments, in no particular order:
Local(0)
for the interpreter context). We should be careful to weed as many of these out as possible (I won't have found all of them!) and make sure we don't introduce any more ni future.x
. Let's kill those.Overall, the aim of this is to make our future selves happier at what our current selves did :) Bear in mind that I'm not familiar with large chunks of the repo, and so some of my comments will be inane, incorrect, or perhaps plain bonkers.