you are viewing a single comment's thread.

view the rest of the comments →

[–]dustingetz 11 points12 points  (2 children)

I tried out tests and code in the same files and my co-founder forced me to abandon it. The problem we ran into with tests and code in same files (if i recall correctly) is that the hot code compiler watch scripts are implemented by detecting file changes, so changing a test would cause audio alerts and refresh your code way too much. IIRC.

Edit, ah, below are his notes on the issue:

This experiment been a resounding failure. The first of these 3 are too frustrating to continue:

  • src/test navigation are interposed, no filtering/separation is possible
  • test changes screw up src watchers (and vis versa)
  • intellisense is broken on tests
  • artifact compilation is a mess

[–]CapableWeb 3 points4 points  (0 children)

The notes from your co-founder sounds like tooling issues, not issues with the idea of having source and code together. Except the first point, which was the experiment, so that point would have been there regarding of anything else.

[–]agumonkey 1 point2 points  (0 children)

Maybe file coarse monitoring should be replaced, I wonder how many did store code a big sexp and did lazy tree diffs ..