Suggestion: change extension of .out files about bisect_ppx HOT 4 CLOSED

I share your observation. The *.out extension is traditionally used by C compilers and a bad choice for that reason. Something like .bsct or similar would be better. Strictly spoken, it is taken, according to this: https://www.file-extensions.org/search/?searchstring=bsct but .bisect would be free.

from bisect_ppx.

We should probably get moving on this.

1. In the next release, add a PPX option -new-extension that causes Bisect_ppx to output .out files files with a new extension. Add a nag to the PPX if the option is not supplied. Alternatively, or additionally, we can add a nag to bisect-ppx-report if it is given .out files. Link to this issue from the nag. This softly informs the users and encourages them to gradually adapt their build system.
2. In 2.0.0, make .bisect the default.
3. In 2.0.0 or a later release, nag users to stop passing -new-extension.

from bisect_ppx.

@rleonid Any thoughts on the extension? I'm suggesting .bisect. Do you think it would cause any problems?

from bisect_ppx.

I wouldn't bother with a nag and just change the extension (.bisect is fine with me).
If we add the appropriate note to changes and maybe an opam message for the new versions we should fine.

from bisect_ppx.