-
Notifications
You must be signed in to change notification settings - Fork 917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error during compilation #4545
Comments
I cannot reproduce this issue. Please provide a full reproducer that shows this problem. Ideally a small but complete code sample (including go.mod and go.sum). Also please share the output of |
Sorry for the cryptic report. Here are the needed info. The btree.Set example in https://github.com/tidwall/btree?tab=readme-ov-file#example is a repro, that is, this code package main
import (
"fmt"
"github.com/tidwall/btree"
)
func main() {
// create a map
var users btree.Map[string, string]
// add some users
users.Set("user:4", "Andrea")
users.Set("user:6", "Andy")
users.Set("user:2", "Andy")
users.Set("user:1", "Jane")
users.Set("user:5", "Janet")
users.Set("user:3", "Steve")
// Iterate over the maps and print each user
users.Scan(func(key, value string) bool {
fmt.Printf("%s %s\n", key, value)
return true
})
fmt.Printf("\n")
// Delete a couple
users.Delete("user:5")
users.Delete("user:1")
// print the map again
users.Scan(func(key, value string) bool {
fmt.Printf("%s %s\n", key, value)
return true
})
fmt.Printf("\n")
// Output:
// user:1 Jane
// user:2 Andy
// user:3 Steve
// user:4 Andrea
// user:5 Janet
// user:6 Andy
//
// user:2 Andy
// user:3 Steve
// user:4 Andrea
// user:6 Andy
} Compiled it with
|
Unfortunately I still cannot reproduce this issue. This is with Can you tell me:
|
Sure. I am using ubuntu 24.04.1 LTS, on a multipass VM in OSX. I manually built tinygo. |
Opened an issue against the llvm-project (llvm/llvm-project#113672), but opening it here as well for awareness.
The error seems to happen when I import this project "github.com/tidwall/btree"
Please close if not appropriate
The text was updated successfully, but these errors were encountered: