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

Future code clean up TODOs: #1

Open
K-Wu opened this issue Aug 18, 2020 · 0 comments
Open

Future code clean up TODOs: #1

K-Wu opened this issue Aug 18, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@K-Wu
Copy link
Collaborator

K-Wu commented Aug 18, 2020

This issue is supposed to be an aggregate list of the TODOs in code clean up efforts (not prioritized at this moment but we might want to work on this some time in the future). In the meantime, please feel free to reply to this thread (if you can't modify it) to add items you deem necessary.

  1. Separate path and other environment variables to an individual configuration file. Developers are expected to not commit it when they make modification to it during local development.

    • including the TEMPLATE_DIR variable in sysgen.py
  2. Add .gitignore

  3. Add a style linter configuration file into the project to govern the style automated check.

    • limit all lines in code to a maximum of 79 characters, as suggested by PEP 8.
  4. There seem to be redundant new line after every for loop in the generated C code. Remove them in the compiler logic if there are.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant