Hi Jason, thanks for your kind words and the helpful suggestion. You are 
right, not having seeds in the examples was a big omission! I've added them 
in 
https://github.com/jellevandenhooff/gosim/commit/6960c38670862405b71ee7f6c06851fa2d19566a:

go run github.com/jellevandenhooff/gosim/cmd/gosim test -v -seeds=1-3 
-run=TestGosim . === RUN TestGosim (seed 1) 1 main/4 14:10:03.000 INF 
examples/simple_test.go:12 > Are we in the Matrix? true method=t.Logf 2 
main/4 14:10:03.000 INF examples/simple_test.go:13 > Random: 
811966193383742320 method=t.Logf --- PASS: TestGosim (0.00s simulated) === 
RUN TestGosim (seed 2) 1 main/4 14:10:03.000 INF examples/simple_test.go:12 
> Are we in the Matrix? true method=t.Logf 2 main/4 14:10:03.000 INF 
examples/simple_test.go:13 > Random: 5374891573232646577 method=t.Logf --- 
PASS: TestGosim (0.00s simulated) === RUN TestGosim (seed 3) 1 main/4 
14:10:03.000 INF examples/simple_test.go:12 > Are we in the Matrix? true 
method=t.Logf 2 main/4 14:10:03.000 INF examples/simple_test.go:13 > 
Random: 3226404213937589817 method=t.Logf --- PASS: TestGosim (0.00s 
simulated) ok translated/github.com/jellevandenhooff/gosim/examples 0.254s 


Op dinsdag 10 december 2024 om 13:20:34 UTC-8 schreef Jason E. Aten:

> Jelle, gosim looks awesome and very cool.  Also thanks for the link to the 
> interesting talk.
>
> How, in gosim, would you set a different seed to change the behavior of 
> the 
> pseudo-random-number-generator based things like maps and 
> goroutine scheduling, Go select statements? It seems
> trying a bunch of different random seeds would be an essential
> part of a test run.  This might be worth putting in the up front examples.
>
> 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 golang-nuts+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/golang-nuts/5b0331f3-61dd-4a72-9da1-12bd197ad1dfn%40googlegroups.com.

Reply via email to