47 lines
1.6 KiB
Markdown
47 lines
1.6 KiB
Markdown
PLEASE ACCEPT MY APPOLOGIES FOR DOING THIS.
|
|
I DID THIS TO MAKE OLD VERSIONS OF GO WORK.
|
|
|
|
If you are reading this, I'm sorry.
|
|
|
|
This probably won't work because of src/runtime/coro.go
|
|
But, it might fucking limp along and maybe fucking compile
|
|
enough of some sort of monster that'll work enough to
|
|
get out of some mess and help find and build golang 1.24
|
|
|
|
GO 1.24 added 'iter' and it is awesome. I want to use
|
|
it and I've converted autogenpb to use it in the auto
|
|
generated Sort() and Gui() functions.
|
|
|
|
The problem is I have so many systems and os's to support
|
|
that I can't be sure that I can even get version 1.24 installed
|
|
which means I can't even compile the tooling I need
|
|
to figure out what is going on.
|
|
|
|
This is because there are so many embedded riscv half ass, broken,
|
|
or poorly configured enviornments that there are no known things.
|
|
Then there are all the hardware design enviornments that are
|
|
complicated. (skywater, tiny tapeout, efabless, etc devs)
|
|
|
|
It's probably going to take me all year to convert everything
|
|
and even know if I can get version 1.24 to work everywhere.
|
|
|
|
This package is more difficult than it should be because
|
|
I couldn't use:
|
|
|
|
internal/race
|
|
internal/abi
|
|
internal/goarch
|
|
|
|
I would vote against having anything in the compiler marked
|
|
as internal/ other than an example of how that feature
|
|
works for the developers that want it. It is NOT a feature
|
|
the compiler itself should use. I would suggest making
|
|
|
|
/internal/example
|
|
|
|
This package would be better as golang.org/iter but I don't
|
|
know who to ask about doing that.
|
|
|
|
coro.go patch:
|
|
~/go/src/go.googlesource.com/go/src/iter$ git whatchanged -1 -p a9c9cc07ac0d3dc73865a57e6ce45c22ada3b5c9
|