- 24 Jan, 2017 1 commit
-
-
Harris Hancock authored
-
- 06 Apr, 2016 1 commit
-
-
Harris Hancock authored
-
- 23 Jun, 2015 1 commit
-
-
Kenton Varda authored
-
- 29 Jan, 2015 1 commit
-
-
Kenton Varda authored
-
- 30 Nov, 2014 1 commit
-
-
Philip Quinn authored
-
- 29 Nov, 2014 1 commit
-
-
Kenton Varda authored
Distinguishing between "local bugs" and "preconditions" was proving difficult in practice, because a precondition failure in one function may very well indicate a bug in a calling function, but the exception may be thrown through that function, thus when caught the classification is nonsensical. The distinction also was not as useful as imagined. So, I eliminated this distinction.
-
- 24 Nov, 2014 1 commit
-
-
Kenton Varda authored
-
- 06 Nov, 2014 1 commit
-
-
Kenton Varda authored
-
- 04 Nov, 2014 1 commit
-
-
Kenton Varda authored
The 'objectId' field is now deprecated. Long-term, each vat will export no more than one "bootstrap interface" which can be obtained via 'Bootstrap'. Restoring SturdyRefs will be accomplished through higher-level interfaces specific to the VatNetwork in use. See comments for 'Bootstrap' in rpc.capnp for more discussion.
-
- 01 Nov, 2014 1 commit
-
-
Philip Quinn authored
This removes all instances of the zero-length brand dependencies arrays (04a9c84d).
-
- 31 Oct, 2014 1 commit
-
-
Philip Quinn authored
-
- 26 Oct, 2014 2 commits
-
-
Kenton Varda authored
Extended discussion: https://groups.google.com/d/msg/capnproto/lRlWBOglQv4/8-Qo96AcZQIJ
-
Kenton Varda authored
To use, pass --disable-reflection to the configure script. This produces a smaller runtime library. However, using it for this purpose is not recommended. The main purpose of lite mode is to define a subset of Cap'n Proto which might plausibly compile under MSVC. MSVC still lacks full support for constexpr and expression SFINAE; luckily, most of our use of these things relates to reflection, and not all users need reflection. Cap'n Proto lite mode inherits its name from Protocol Buffers' lite mode. However, there are some key differences: - Protobuf generated code included global constructors related to registering descriptors and extensions. For many people, this was the main reason to use lite mode: to get rid of these global constructors and achieve faster startup times. Cap'n Proto, on the other hand, never had global constructors in the first place. - Schemas are actually still available in lite mode, though only in their raw (Cap'n Proto structure) form. Only the schema API (which wraps the raw schemas in a more convenient interface) and reflection API (which offers a convenient way to use the schemas) are unavailable. - Lite mode is enabled in an application by defining CAPNP_LITE rather than by specifying an annotation in the schema file. This better-reflects real-world usage patterns, where you typically want to enable lite mode application-wide anyway. - We do not build the lite mode library by default. You must request it by passing --disable-reflection to the configure script. Before you can do that, you must have a prebuilt Cap'n Proto compiler binary available, since the compiler can't be built without reflection. - Relatedly, the lite mode library is built with the same name as the full library. This library is not intended to be installed. If anything it should be statically linked. But, mostly the option only exists on non-MSVC platform to give us a way to test that we haven't broken lite mode.
-
- 24 Oct, 2014 1 commit
-
-
Kenton Varda authored
-
- 23 Oct, 2014 1 commit
-
-
Kenton Varda authored
Note that embedded schema structures in generated code are still incorrect.
-
- 20 Oct, 2014 1 commit
-
-
Kenton Varda authored
That is to say, whereas previously we would extend capnp::typeId<T>() to a new type by declaring a specialization of it for that type, now we instead have the type contain a nested class called _capnpPrivate which contains a `typeId` constant. This is necessary because it is impossible to specialize a template for a type which is itself nested inside a template type. E.g. it's impossible to write a specialization `template <typename T> typeId<Foo<T>::Bar>()`; C++ simply doesn't support this. But with generics, Cap'n Proto will allow types to be nested inside templates, so we need this to work.
-
- 17 Oct, 2014 1 commit
-
-
Kenton Varda authored
-
- 11 Oct, 2014 1 commit
-
-
Kenton Varda authored
-
- 11 Sep, 2014 1 commit
-
-
Kenton Varda authored
-
- 05 May, 2014 1 commit
-
-
Kevin Wallace authored
This allows {schema,rpc,rpc-twoparty}.capnp to be used without modification when relocated outside of the Cap'n Proto codebase.
-
- 10 Feb, 2014 1 commit
-
-
Kenton Varda authored
-
- 22 Dec, 2013 1 commit
-
-
Kenton Varda authored
-
- 10 Dec, 2013 1 commit
-
-
Kenton Varda authored
Define additional type aliases AnswerId and ImportId. In the RPC protocol, always use the type corresponding to the sender's point of view. In the implementation, always use the type corresponding to the local point of view.
-
- 06 Dec, 2013 1 commit
-
-
Kenton Varda authored
Change capability pointers to be indexes into a separate cap list so that CapDescriptors can be interpreted on receipt rather than delaying until the application actually traverses the message. This massively simplifies a lot of things.
-
- 23 Nov, 2013 1 commit
-
-
Kenton Varda authored
Tail calls half-implemented, but I think it's time to delete all the cancellation code before continuing because it will simplify things.
-
- 22 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 21 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 18 Nov, 2013 1 commit
-
-
Kenton Varda authored
-
- 14 Nov, 2013 1 commit
-
-
Kenton Varda authored
In RPC protocol, rename request -> params, answer -> results. Also fix up Join stuff in rpc-twoparty.capnp, because it was sort of wrong.
-
- 08 Nov, 2013 1 commit
-
-
Kenton Varda authored
Implement two-party network. The first RPC call over a socket took place at 2013-11-08 14:46:43 -0800 and completed successfully.
-
- 31 Oct, 2013 1 commit
-
-
Kenton Varda authored
-