You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The provided example project that shows how to use custom types in avo generated asm functions depends on using a handcrafted stub.go file that is not overwritten by using a -stubs parameter.
It would be a very handy minor change to be able to specify one or more import statements to insert in generated stubs so that large/complex stub files don't need to be hand maintained as the example requires.
Which could then generate with: //go:generate go run asm.go -out ext.s -stubs stub.go and generate a corresponding stub:
// Code generated by command: go run asm.go -out ext.s -stubs stub.go. DO NOT EDIT.package ext
import"github.com/mmcloughlin/avo/examples/ext/ext"// StructFieldB returns field B.funcStructFieldB(e ext.Struct) byte
The text was updated successfully, but these errors were encountered:
The provided example project that shows how to use custom types in avo generated asm functions depends on using a handcrafted
stub.go
file that is not overwritten by using a-stubs
parameter.It would be a very handy minor change to be able to specify one or more import statements to insert in generated stubs so that large/complex stub files don't need to be hand maintained as the example requires.
I'm imagining something like:
Which could then generate with:
//go:generate go run asm.go -out ext.s -stubs stub.go
and generate a corresponding stub:The text was updated successfully, but these errors were encountered: