Component: (Internal) Developer Experience

[StachuDotNet]

This issue organizes work around how nice it is to actually contribute to dark. Are the ideas accessible? Are things documented? Are there OSs we don't run well on? If you have any questions about getting started, or issues, let us know here.

• Revisit how to test/validate docstrings (see old Revisit how to test/validate docstrings #4762)
• Port our scripts to Darklang
• Somehow report on types allow<>'d to be serialize that are unused
• Decide between init, lazy, and passing values for startup values and singletons (see Decide between init, lazy and passing values for startup values/singletons. #3944)
• Lock dotnet tool versions in Dockerfile (see Lock dotnet tool versions in Dockerfile #3896)
• Run F# backend against coverage tool (see Run F# backend against coverage tool #3688)
• Document/Fix F# Debugging (see Document/Fix F# Debugging #3634)
• Consider banning string function (see Consider banning string function #3567)
• Improve safety of our duplicate dockerfile setup
  • we have a separate repo, dockerfile, that is maintained and built to produce a base image for CI to use while building
  • we aim to keep the Dockerfile in this repo (along with a few associated scripts) a direct match of the one in the dockerfile repo
  • TODO: somehow, try to ensure these files don't become "out of sync"
  • fail if behind, in CI, on main
  • utilities to copy ... built in dark
• make builds faster
  • ? interface (.fsi) files might improve compile-time performance.
    • they seemingly can be auto-generated: https://twitter.com/tomasgrosup/status/1584460711538802688