add typecasting to RTEST macro
Add sorting of options by displayName.
Enlist interruptible Regexp match in Thread#kill/raise. Fixes #792
Remove rogue stat-caching logic that was not ready for release.
Remove tests for compile property change affecting new runtimes.

Properties should generally be treated as read-only once you boot,
since they're basically global state that affects everyone. My
recent commits for Option logic added caching of the loaded value
after first load, to avoid the overhead of re-loading and
re-parsing it every time. Reloads can be forced, but I tend to
think properties are boot-time configuration that shouldn't be
twiddled at runtime. With that in mind, these tests and their
expectations are no longer valid.
Remove -b testing from test_command_line_switches.

-b was not supported and not really useful, so it was removed
recently. This test was not updated to remove it.
Update to jruby-launcher 1.0.17 which won't test on install.
Fix String performance regression

Port the single byte COW heuristic from the 1.8 code path to 1.9.

This fixes #168.
Merge pull request #784 from unbit/master

add typecasting to RTEST macro
Merge branch 'string-optimize' of git://github.com/dmarcotte/jruby into dmarcotte-string-optimize
Checking for size of outgoing and incoming edges of the vertex after
removing a single edge

- After removing all incoming or outgoing edges, incoming or outgoing
  edges of a vertex are set to null
- But after removing a single edge, it is not checked that outgoing of
  the source or incoming of the destination should be changed to null
  or not
- This commit checks that condition and sets outgoing and incoming of
  source and destination respectively to null if the condition is met.
Add IR specs to Travis

Allow them to fail; IR is still experimental and specs are scant.
Merge pull request #771 from prathamesh-sonpatki/vertex_specs

Checking for size of outgoing and incoming edges of the vertex after removing a single edge
invalidate constant cache if included module has constants
remove qualified const_get test
Synchronize hash resizing, to avoid hangs under concurrent load.

This change, suggested by Masayuki Onjo, improves the thread-
safety of Hash by preventing two resizes from occurring at the
same time. Such a situation can lead to a bucket's chain of nodes
looping back on itself in the following way:

* Thread A begins re-inserting elements from the old bucket
  list into the new bucket list. Elements that will go into
  the same bucket in the new list must be chained. As they
  are inserted, they become the new bucket head, pointing at
  whatever was in the bucket already.
* Nodes X and Y would go into the same bucket in the new hash.
* Thread A proceeds to puts X into the bucket; X.next = null.
* Thread A proceeds with Y. Y.next = X.
* At the same time, thread B begins performing the same resize
  operation against its own new bucket list.
* Thread B proceeds to insert X. X.next = null.
* Thread B proceeds with Y, saving its next value X. Y.next = X.
* Thread B continues to X, because it must handle all chained
  nodes in the bucket where it found Y. It finds Y already in the
  new bucket where it inserts X. X.next = Y.
* At this point, X.next = Y and Y.next = X, so walking the bucket
  will cause an infinite loop. The Hash is broken.

Making the resize operation synchronized prevents two resizing
threads from mixing old node chaining with new node chaining,
reducing the likelihood of a broken hash.

This does not, however, make Hash thread-safe. Inserts can still
be lost if one thread adds an element during a resize operation,
or elements can end up in the wrong buckets if updated during
a resize (because their effective hash will change after the
resize has already re-inserted the element). We will continue to
explore ways to improve the thread-safety of Hash.
Add some whitespace for readability.
No reason for a null fillInStackTrace to be synchronized.
add test
Merge pull request #795 from charliesome/invalidate-constant-cache-if-included-module-has-constants

Invalidate constant cache if included module has constants