We should add a check to slicec which keeps track of which paths it's written generated code to.
And if a single path would be written to more than once (in a single compilation run), we should issue a warning that the file was overwritten.
This could happen for a variety of reasons, and it's simpler for slicec to handle it, then asking each code-generator to include this check.
We should add a check to
slicecwhich keeps track of which paths it's written generated code to.And if a single path would be written to more than once (in a single compilation run), we should issue a warning that the file was overwritten.
This could happen for a variety of reasons, and it's simpler for
slicecto handle it, then asking each code-generator to include this check.