go-capnp icon indicating copy to clipboard operation
go-capnp copied to clipboard

Cap'n Proto library and code generator for Go

Results 87 go-capnp issues
Sort by recently updated
recently updated
newest added

This came up when @lthibault and I were discussing flow control; `.Ack()` is confusing in that it's not sending an acknowledgement or anything like it; rather, it spawns a goroutine...

cleanup

This is a small refactor that aims for an incremental improvement to `fileparts.go`'s readability. I had to stare at the `imports` struct a wee bit longer than I would have...

cleanup

Now that we have support for mapping `:Capability` types to `capnp.Client`, it might make sense to add a `List[Client]` wrapper, along the same lines as #247. Thoughts?

enhancement

_From @zombiezen on August 6, 2015 21:1_ The `CapDescriptor` struct has a `senderPromise` field which `rpc.Conn` does not support, along with the corresponding `Resolve` message. The Go implementation does not...

bug

Passing an expired capability to `rpc.Conn.Bootstrap` causes a deadlock. To reproduce, run `TestHandleReturn_regression` in the `bug/bootstrap-panic` branch. The second subtest relates to the present issue. ```go func TestDeadlock(t *testing.T) {...

bug

This is a great library, and I'm getting a lot of use out of it. However, it's very complicated and the learning curve is high. It would be great if...

@lthibault, I started playing with my own ideas about how to clean up process lifecycle management. I'm curious to your thoughts, particularly regarding. - Whether you think the proc package...

As per #257 this effort would avoid the need to instantiate an encoder/decoder for single messages. @zenhack My interpretation of [your comment](https://github.com/capnproto/go-capnproto2/issues/257#issuecomment-1175237862) is that this is pure syntactic sugar, and...

enhancement
good first issue

There's a deadlock footgun that I hit while writing tests for #213. Roughly, if you do: ``` foo.Method(ctx, func(p Foo_method_Params) error { p.SetFoo(foo) return nil }) ``` ...on a remote...

bug

It seems to be fairly common for a user to call `NewFoo` for some struct `Foo` when they should have called `NewRootFoo`, and end up with a message with no...