Casper

Lazy verification

2

### Discussed in https://github.com/google/flatbuffers/discussions/7125 (repost for visibility) Originally posted by **CasperN** February 22, 2022 Our current verifiers were implemented eagerly, where we read and verify every single field/element in the...

This is needed in codebases where CheckReturnValue is on by default

Namer TS

1

Apply Namer to typescript code generation #7142

@dbaileychess how do we feel about a release? Requested in #7273 I could try giving this one a go if https://github.com/google/flatbuffers/wiki/FlatBuffers-release-process is up to date Reading #6967, it seems like...

RFC: Centralize naming convention

18

Currently, the various code generators reinvent their own ways to escape keywords and recase identifiers to fit with local style. DRY style concerns aside, the manual approach might not be...

Add an option for checking for valid bits is in the getter rather than constructor

5

Hi, I want to use bitflags for generated code that interacts with data in other languages, some of which are bitflags (https://github.com/google/flatbuffers/pull/6098). I don't want to drop data so I'd...

Parser refactoring proposal

12

As I tend to do, I'll try to keep this top comment updated with the latest state. This is based off of https://github.com/google/flatbuffers/issues/6428#issuecomment-856272970. # Proposal ## Why `flatc` is really...

The Rust Flatbuffers library currently relies on Rust's notion of alignment, which is platform dependent. We should audit/remove all use of `align_of::() ` and use our own trait for flatbuffers...

#7142

The main release tracker is at #6636, and this issue is just for Rust and its breaking changes. * [ ] Stop generating code with `#deperacated` markers, I promised they'd...