Please do not depend on autogenerated names of destruct that are sensitive to the file in which records are defined

[JasonGross]

My bug minimizer cannot fully minimize the example at coq/coq#14798 (comment) because

verdi/core/GhostSimulations.v

Lines 86 to 88 in 002da48

	destruct net.
	concludes.
	destruct nwState. auto.

relies on the fact that the record Verdi.Net.network is defined in some file other than GhostSimulations.v (in this case, in the file Net.v). This is an instance of coq/coq#3523.

Suggested fixes:

-  destruct net.
+  destruct net as [? nwState].
   concludes.
   destruct nwState.

or

   destruct net.
   concludes.
-  destruct nwState.
+  let nwState := match goal with H : data |- _ => H end in destruct nwState.

[palmskog]

@JasonGross I can apply one of the fixes, but which one do you recommend? (A PR is also welcome.)

[JasonGross]

I'd suggest whichever one is more robust to future changes: the former is more robust to the changes in the specific types of the fields and the presence of new context variables, while the latter is more robust to changes in field ordering. Which of these seems more important to be robust to? (Said another way, which better captures the essence of the proof: "destruct the second field of net a second time" or "destruct the first thing in the context of type data"?)
(If they seem equally relevant, I'd lean towards the first one, since it's fewer characters and probably easier for humans to read.)