Quickly checking that a string belongs to a small set

• gperf

  7 2 4.7 C++

  mirror of git.savannah.gnu.org/gperf.git with more features. gitlab has the issues

• Nginx

  99 20,211 8.9 C

  An official read-only mirror of http://hg.nginx.org/nginx/ which is updated hourly. Pull requests on GitHub cannot be accepted and will be automatically closed. The proper way to submit changes to nginx is via the nginx development mailing list, see http://nginx.org/en/docs/contributing_changes.html

  

nginx uses switch on a combination of length + specific known characters as part of a similar optimization.

https://github.com/nginx/nginx/blob/9c7a2c7ce4ad02a36df1bb0e...

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• string-case

  1 14 10.0 Common Lisp

  Excessive macro that generates decision trees for small sets of strings

This reminds me of the Paul Khuong's string-case macro in Common Lisp.

https://github.com/pkhuong/string-case/blob/master/string-ca...

• nbperf

  2 13 0.0 C

  Improved NetBSD's Perfect Hash Generation Tool v3

• asm

  4 845 0.0 Go

  Go library providing algorithms optimized to leverage the characteristics of modern CPUs (by segmentio)

  

We took a similar approach in our JSON decoder. We needed to support sets (JSON object keys) that aren't necessarily known until runtime, and strings that are up to 16 bytes in length.

We got better performance with a linear scan and SIMD matching than with a hash table or a perfect hashing scheme.

See https://github.com/segmentio/asm/pull/57 (AMD64) and https://github.com/segmentio/asm/pull/65 (ARM64). Here's how it's used in the JSON decoder: https://github.com/segmentio/encoding/pull/101

• encoding

  8 962 3.6 Go

  Go package containing implementations of efficient encoding, decoding, and validation APIs.

  

We took a similar approach in our JSON decoder. We needed to support sets (JSON object keys) that aren't necessarily known until runtime, and strings that are up to 16 bytes in length.

We got better performance with a linear scan and SIMD matching than with a hash table or a perfect hashing scheme.

See https://github.com/segmentio/asm/pull/57 (AMD64) and https://github.com/segmentio/asm/pull/65 (ARM64). Here's how it's used in the JSON decoder: https://github.com/segmentio/encoding/pull/101

Suggest a related project