Nevkontakte

Results 128 comments of Nevkontakte

My gut feeling is that the bug lays at the border between how gopherjs caches intermediate build results and how go/types checks for type equality. I suspect that go/types relies...

I spent a bunch of time with the debugger and tracked down the error source. ## How the error happens? The failing check is test whether time.Time is assignable to...

/cc @dmitshur in case he knows something useful about `gcexportdata` format.

I wrote a quick and dirty benchmark to confirm whether this is still the case: ```go package main import ( "regexp" "runtime" "testing" ) var sideEffect interface{} func BenchmarkCompile(b *testing.B)...

The codebase have moved on too far to make this pull request easily mergeable, but I think the approach it takes is a good one. Recently merged https://github.com/gopherjs/gopherjs/pull/1105 set up...

Despite #291, this seems to still be an issue: ```go package main import ( _ "oink" ) func main() { } ``` ``` $ gopherjs build cannot find package "oink"...

@benma it is possible to make GopherJS output behave like a single CommonJS module — it's mostly a matter of exporting the interfaces you want via `js.Module`. Though I haven't...

~Was there no RC this time?~ _(Edit: I should get more sleep, betas come before rc)_. In any case, it's time indeed. I propose to separate generics support from the...

I've created a new [go1.18-wip](https://github.com/gopherjs/gopherjs/tree/go1.18-wip) branch to do the work in. Here's an easy recipe to start working on 1.18 support: ``` $ go install golang.org/dl/go1.18beta1@latest $ go1.18beta1 download $...

My [go1.18-wip](https://github.com/nevkontakte/gopherjs/tree/go1.18-wip) branch now has complete Go 1.18 compatibility with the exception of generics, which brings us to the question of our approach to the release. I plan to start...