Dead code tracking #83

Open
opened 2023-01-12 21:32:50 +00:00 by deavmi · 0 comments
Owner

What is this?

There are some pieces that are technicall dead code but are kept in case there were intended to be extended or were part of something but we should list them here to track them so we know if we can quickly remove them at any given time.

typecheck/core.d

  • checkDefinitionTypes(Container c)
    • This has no apparent use. It will generate an array of Class[] called classes and then immediately dispose of it upon returning.
  • funcCall handler
    • There is a pushback that never occurs and such logic is dumb - no pushbacks should ever be prevalent anywhere in the processor
    • See issue #101
## What is this? There are some pieces that are technicall dead code but are kept in case there were intended to be extended or were part of something but we should list them here to track them so we know if we can quickly remove them at any given time. ### `typecheck/core.d` - [ ] `checkDefinitionTypes(Container c)` * This has no apparent use. It will generate an array of `Class[]` called `classes` and then immediately dispose of it upon returning. - [ ] `funcCall handler` * There is a pushback that never occurs and such logic is dumb - no pushbacks should **ever** be prevalent anywhere in the processor * See issue #101
deavmi added reference vardec_varass_dependency 2023-01-12 21:32:57 +00:00
deavmi self-assigned this 2023-01-12 21:33:00 +00:00
deavmi added this to the Dependency tree, type-checking and codegen project 2023-01-12 21:33:03 +00:00
deavmi added this to the Basics milestone 2023-01-12 21:33:05 +00:00
deavmi added the
typing
label 2023-01-12 21:33:10 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tlang/tlang#83
No description provided.