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

Split functions into front-end and back-end functions #2

Open
4 tasks
jarmuszz opened this issue Aug 28, 2021 · 0 comments
Open
4 tasks

Split functions into front-end and back-end functions #2

jarmuszz opened this issue Aug 28, 2021 · 0 comments
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@jarmuszz
Copy link
Owner

jarmuszz commented Aug 28, 2021

Currently, some user functions call other user functions which is a really bad practice. Some functions should be split into front-end and back-end parts (like _tree and intern_tree) where front-end function handles arguments and error-checking and calls the back-end function/s.

Split like this will not only improve performance but will also fix bugs and and make debugging easier.

Functions to split:

  • _goto
  • _find
  • _source_info
  • _unset_info
  • And probably others
@jarmuszz jarmuszz added bug Something isn't working enhancement New feature or request labels Aug 28, 2021
@jarmuszz jarmuszz added this to the v0.2 release milestone Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant