-
Notifications
You must be signed in to change notification settings - Fork 35
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
Refactor handlers' code #105
Comments
@jvcoutinho could you please list them in priority order? hardest to understand first. |
I believe it's more an issue of operation simplification and code duplication reduction. The intention behind the code is clear. Deletions -> Type Ambiguity Error -> Initialization Blocks (old) -> Renaming/Deletion (old) -> New Element Referencing Edited One -> Duplicated Declaration |
But they do not be to have a priority order to execute (at least it was not
meant to), right?
Em qui, 12 de set de 2019 às 09:19, João Victor <[email protected]>
escreveu:
… I believe it's more an issue of operation simplification and code
duplication reduction. The intention behind the code is clear.
Deletions -> Type Ambiguity Error -> Initialization Blocks (old) ->
Renaming/Deletion (old) -> New Element Referencing Edited One -> Duplicated
Declaration
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#105>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAZN6XOTL3F4HTF3LYKBY3TQJIXVJANCNFSM4IVHAXGQ>
.
|
Right. It's another issue. |
Some of them are hard to understand.
The text was updated successfully, but these errors were encountered: