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

convert TODO comments from source code into issues #363

Open
andrewrk opened this issue May 5, 2017 · 4 comments
Open

convert TODO comments from source code into issues #363

andrewrk opened this issue May 5, 2017 · 4 comments
Labels
bug Observed behavior contradicts documented or intended behavior
Milestone

Comments

@andrewrk
Copy link
Member

andrewrk commented May 5, 2017

Before releasing 1.0.0, "TODO" should occur exactly 0 times in the source code. If there's an issue it should be documented on the issue tracker. Source code can link to an issue if it seems appropriate.

@andrewrk andrewrk added the bug Observed behavior contradicts documented or intended behavior label May 5, 2017
@andrewrk andrewrk added this to the 1.0.0 milestone May 5, 2017
@andrewrk andrewrk modified the milestones: 1.0.0, 0.2.0 Oct 19, 2017
@andrewrk andrewrk modified the milestones: 0.2.0, 0.3.0 Jan 8, 2018
@andrewrk andrewrk modified the milestones: 0.3.0, 0.4.0 Feb 28, 2018
andrewrk added a commit that referenced this issue Apr 25, 2018
See #363

For Complex as a builtin type, see discussion in #949
@andrewrk andrewrk modified the milestones: 0.4.0, 0.5.0 Feb 5, 2019
@andrewrk
Copy link
Member Author

andrewrk commented May 3, 2019

Also look for "NOTE" and "XXX". Some contributors have been using those.

@daurnimator
Copy link
Contributor

@andrewrk
Copy link
Member Author

Also look for FIXME.

andrewrk added a commit that referenced this issue Sep 15, 2020
Before merging, do this for every item in the file:
 * solve the issue, or
 * convert the task to a github issue and update the comment
   to link to the issue (and remove "TODO" text from the comment).
Then delete the file.

Related: #363
andrewrk added a commit to hoanga/zig that referenced this issue Feb 25, 2021
 * no isHaiku() function since there is not more than one os tag that
   this applies to.
 * clean up some control flow into a switch
 * add some TODO comments to investigate panics that suspiciously look
   like they should be compile errors (see ziglang#363)
dgbuckley pushed a commit to dgbuckley/zig that referenced this issue Mar 9, 2021
 * no isHaiku() function since there is not more than one os tag that
   this applies to.
 * clean up some control flow into a switch
 * add some TODO comments to investigate panics that suspiciously look
   like they should be compile errors (see ziglang#363)
andrewrk added a commit to g-w1/zig that referenced this issue Jun 21, 2021
andrewrk added a commit to g-w1/zig that referenced this issue Jun 22, 2021
@nektro
Copy link
Contributor

nektro commented Aug 30, 2021

Also look for deprecated, moved inside of @compileErrors.

andrewrk added a commit that referenced this issue Dec 4, 2024
See #363. Please file issues rather than making TODO comments.
andrewrk added a commit that referenced this issue Dec 6, 2024
See #363. Please file issues rather than making TODO comments.
andrewrk added a commit that referenced this issue Dec 7, 2024
See #363. Please file issues rather than making TODO comments.
andrewrk added a commit that referenced this issue Dec 12, 2024
See #363. Please file issues rather than making TODO comments.
andrewrk added a commit that referenced this issue Dec 13, 2024
See #363. Please file issues rather than making TODO comments.
andrewrk added a commit that referenced this issue Dec 14, 2024
See #363. Please file issues rather than making TODO comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Observed behavior contradicts documented or intended behavior
Projects
None yet
Development

No branches or pull requests

3 participants