flatbuffers
No description set
- Developed at devel:libraries:c_c++
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:zSystems/flatbuffers && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
flatbuffers-23.3.3.tar.gz | 0002197401 2.1 MB | |
flatbuffers.changes | 0000012000 11.7 KB | |
flatbuffers.spec | 0000003467 3.39 KB | |
python-flatbuffers.changes | 0000001367 1.33 KB | |
python-flatbuffers.spec | 0000001572 1.54 KB |
Revision 10 (latest revision is 13)
Dominique Leuenberger (dimstar_suse)
accepted
request 1074771
from
Dirk Mueller (dirkmueller)
(revision 10)
- update to 23.3.3: * Major release! Just kidding, we are continuing the versioning scheme of using a date to signify releases. This results in the first release of the new year to bump the tradition major version field. * Refactoring of flatc generators to use an interface (#7797). * Removed legacy cmake support and set min to 3.8 (#7801). * Reworked entry points for Typescript/Javascript and compatibility for single file build (#7510) * Removed go.mod files after some versioning issues were being report (#7780). * Go minimum version is now 1.19 (#7720) with the addition of Go modules. * Added CI support for Big Endian regression testing (#7707). * Fixed getFullyQualifiedName in typescript to return name delimited by '.' instead of '_' (#7730). * Fixed the versioning scheme to not include leading zeros which are not consistently handled by every package manager. Only the last release (12.12.06) should have suffered from this. * 20 Major releases in a row? Nope, we switched to a new versioning scheme that is based on date. * Python supports fixed size arrays now (#7529). * Behavior change in how C++ object API uses UnPackTo. The original intent of this was to reduce allocations by reusing an existing object to pack data into. At some point, this logic started to merge the states of the two objects instead of clearing the state of the packee. This change goes back to the original intention, the packed object is cleared when getting data packed into it (#7527).
Comments 0