Unexpected go output
Open
Nobody has claimed this yet.
to be confirm
- Dominant language
- Go
- Stars
- 33
- Forks
- 11
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 51
Description
package freertos
import (
"github.com/goplus/lib/c"
_ "unsafe"
)
type Struct (unnamed at /Users/haolan/esp/esp-idf/components/espRom/esp32s3/include/esp32s3/rom/md5Hash.h:28:8) struct {
Buf [4]c.Uint32T
Bits [2]c.Uint32T
In [64]c.Uint8T
}
// llgo:link (*MD5Context).MD5Init C.MD5Init
func (recv_ *MD5Context) MD5Init() {
}
// llgo:link (*MD5Context).MD5Update C.MD5Update
func (recv_ *MD5Context) MD5Update(buf *c.Char, len c.Uint) {
}
//go:linkname MD5Final C.MD5Final
func MD5Final(digest *c.Char, context *MD5Context)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides only the generated Go/C interop output and no source file or test. Start by reproducing the generation for the shown C declarations, then trace the generator entry point that emits these bindings; done means the unexpected output is explained and the behavior is covered by an appropriate regression test or documented as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100