StudioInfinity/dyna3
2
0
Fork 2
Code Issues 65 Pull requests 2 Projects 3 Releases 4 Wiki Activity Actions
Page: Code flags
Pages
Algebraic constraint-solving Code flags Coding environment Constraints Constructions Continuous integration Demo project details Display: Ganja.js Display benchmarking Display Elements and observables Entities Geometric algebra Gram matrix parameterization Home Impossolid Interface Language benchmarks Licensing Logging Numerical optimization References Serialization Symmetry of constraints Test problems User Stories
3 Code flags
Vectornaut edited this page 2025-10-03 20:47:10 +00:00

In the source code, we're using the following flags to mark things we'd like to come back to.

  • /* DEBUG */ Code that was added on the fly for debugging. It should eventually be either removed or replaced with more formal diagnostics, depending on whether we're finding it useful in the long term.
  • /* KLUDGE */ A sloppy, awkward, or fragile way to get something working. It should eventually be replaced with something more polished, elegant, and robust.
  • /* TO DO */ A task involving this code that we should eventually do. The task may be either circumscribed (like replacing a literal with a named constant) or open-ended (like looking into alternatives for an algorithm that we're using). The task may be blocked by tasks outside our control (like the stabilization of an experimental Rust feature).

Searching the source code for these flags can be a good way to remind ourselves of what we want to do. At some point, it might be nice to set up a system for giving each flag a corresponding issue.