Date | Commit message (Collapse) |
|
Oops.
|
|
Thanks to 9d30be3b14e56293cb8402e8c820b89a77460b73[1]
for reporting this via private email on 2014-10-03T00:55:55Z
[1] - (printf "firstname lastname" | sha1sum)
|
|
In our case, it was actually harmless because tdb_errorstr
only returns trusted data, but the warning is ugly.
|
|
st.h should probably not be part of the public Ruby API,
and it may well be removed one day (I would support it).
|
|
It's the preferred hash function nowadays by Ruby itself, so it
probably makes sense to add it
|
|
It'll be OK to use rb_thread_call_without_gvl when
rb_thread_blocking_region is not detectable at all.
We still use rb_thread_blocking_region for Ruby 2.0-2.1 because
rb_thread_call_without_gvl was detectable in 1.9.3, but not
usable as an internal symbol.
ref: https://bugs.ruby-lang.org/issues/9502
|
|
|
|
force inline didn't work for non-static functions (probably without
extern), and we didn't need non-static functions in those cases
anyways, so just use static inline and trust the compiler to do
its thing.
|
|
We don't want path names silently truncated when passed to
the C API.
|
|
This is faster for larger keys on x86_64
|
|
It should be slightly faster than murmur2
|
|
This allows apps to reduce GC thrashing by reusing
a string buffer.
|
|
TDB objects aren't created often, so this shouldn't
be noticeable, and there's no other way if any notion
of thread-safety is desired.
|
|
It's nice to have common hash functions available...
|
|
TDB#clear maps to tdb_wipe_all and TDB#repack maps
to TDB#repack.
|
|
Thread-safety is useful sometimes and needless overhead
otherwise. Default to whatever TDB upstream defaults to.
|
|
This appears to be needed on x86 Debian Lenny but not x86_64
|
|
We still need a lot of work in this area, but this is better
than nothing.
|
|
|
|
|