272 I decided to create a different build for Type IIS incompatible parts:
"did not build" was used for parts planned for build, but removed because they were not Type IIS compatible
"unable to build" was used for parts planned for build, but could not be synthesized by TWIST (whether due to TWIST's pre-synthesis validation, or in actual product delivery)
In terms of future synthesis runs, if were to validate parts beforehand, we would not have added them to the build list (assuming we continue with Type IIS). Whereas for the "unable to build," we may want to retry synthesizing them at TWIST and/or another provider.
If this is a distinction is a bad idea, mechanically, it's easy to combine them under "unable to build". Also up for a better name.
272 I decided to create a different build for Type IIS incompatible parts:
In terms of future synthesis runs, if were to validate parts beforehand, we would not have added them to the build list (assuming we continue with Type IIS). Whereas for the "unable to build," we may want to retry synthesizing them at TWIST and/or another provider.
If this is a distinction is a bad idea, mechanically, it's easy to combine them under "unable to build". Also up for a better name.