Looks interesting! Is there an article somewhere that explains why each change to Go was necessary for DST? For example, why are sticky channel values required for DST? Couldn’t sticky values be simulated with a goroutine that owns sending on a channel that implements the sticky/unsticky/clear behavior? Isn’t it possible in general to arrange to not close a channel more than once?
> On Oct 30, 2025, at 12:48 AM, Jason E. Aten <[email protected]> wrote: > > If you ever wished for > > + better Deterministic Simulation Testing (DST) support, or > > + that channels could replace Condition Variables, or for > > + a sync.WaitGroup alternative that could be interrupted by a timeout, or that > > + channel close could be idempotent and broadcast a non-zero value, > > then I invite you to experiment with my superset-of-Go experiment, Pont. > > https://github.com/glycerine/pont > > Feedback welcome -- post an issue on the repo. > > Jason > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To view this discussion visit > https://groups.google.com/d/msgid/golang-nuts/c7dc4d42-0f31-4960-9497-a7855827b444n%40googlegroups.com > > <https://groups.google.com/d/msgid/golang-nuts/c7dc4d42-0f31-4960-9497-a7855827b444n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/A8CE9148-ADA8-4140-A9FE-93BE4CE2DD48%40willfaught.com.
