we only have a few minutes left. my vote on RFC 26 is: close, for the following reasons:
- it is not difficult to implement this functionality in-place and in my view this will usually be worth it because it will be integrated with some wider reset or clocking scheme
- having three new classes for this purpose does not have a high enough utility for the increase in our API surface
- the functionality could be implemented in an external library and later pulled in if we find that it was widely useful
and the following note:
- if we add `EnableSignal` and `platform.unsafe_add_multicycle_constraint`, we can add something like `FixedStrobeGenerator` as it will provide a clear safety benefit