| layout | toc_group | link_title | permalink |
|---|---|---|---|
docs-experimental |
ruby |
Compatibility |
/reference-manual/ruby/Compatibility/ |
TruffleRuby aims to be fully compatible with the standard implementation of Ruby, MRI, version 2.7.4, including C extensions. TruffleRuby is still in development, so it is not 100% compatible yet.
TruffleRuby can run Rails and is compatible with many gems, including C extensions. TruffleRuby passes around 97% of ruby/spec, more than any other alternative Ruby implementation.
Any incompatibility with MRI is considered a bug, except for rare cases detailed below. If you find an incompatibility with MRI, please report it.
TruffleRuby tries to match the behavior of MRI as much as possible. In a few limited cases, TruffleRuby is deliberately incompatible with MRI in order to provide a greater capability.
TruffleRuby defines these constants for identification:
RUBY_ENGINEis'truffleruby'.RUBY_VERSIONis the compatible MRI version.RUBY_REVISIONis the fullgitcommit hash used to build TruffleRuby (similar to MRI 2.7+).RUBY_RELEASE_DATEis thegitcommit date.RUBY_PATCHLEVELis always zero.RUBY_ENGINE_VERSIONis the GraalVM version, or0.0-and the Git commit hash if your build is not part of a GraalVM release.
In the C API, the preprocessor macro TRUFFLERUBY is defined, which can be checked with #ifdef TRUFFLERUBY.
Continuations are obsolete in MRI, and Fibers are recommended instead.
Continuations and callcc are unlikely to ever be implemented in TruffleRuby, as their semantics fundamentally do not match the JVM architecture.
You cannot fork the TruffleRuby interpreter.
The feature is unlikely to ever be supported when running on the JVM but could be supported in the future in the native configuration.
The correct and portable way to test if fork is available is:
Process.respond_to?(:fork)The following standard libraries are unsupported:
continuation(obsolete in MRI)dbmgdbmsdbmdebug(could be implemented in the future, use--inspectinstead)profile(could be implemented in the future, use--cpusamplerinstead)profiler(could be implemented in the future, use--cpusamplerinstead)io/console(partially implemented, could be implemented in the future)io/wait(partially implemented, could be implemented in the future)pty(could be implemented in the future)win32(only relevant on Windows)win32ole(only relevant on Windows)
TruffleRuby provides its own backend implementation for the ffi gem, similar to JRuby.
This should be completely transparent and behave the same as on MRI.
The implementation should be fairly complete and passes all the specs of the ffi gem except for some rarely-used corner cases.
$SAFE and Thread#safe_level are 0 and no other levels are implemented.
Trying to use level 1 will raise a SecurityError.
Other levels will raise ArgumentError as in standard Ruby.
See the security notes for more explanation on this.
RubyVM is not intended for users and is not implemented.
In MRI, threads are scheduled concurrently but not in parallel. In TruffleRuby threads are scheduled in parallel. As in JRuby and Rubinius, you are responsible for correctly synchronising access to your own shared mutable data structures, and TruffleRuby will be responsible for correctly synchronising the state of the interpreter.
TruffleRuby threads may detect that they have been interrupted at different points in the program compared to where they would on MRI. In general, TruffleRuby seems to detect an interrupt sooner than MRI. JRuby and Rubinius are also different from MRI; the behavior is not documented in MRI, and it is likely to change between MRI versions, so it is not recommended to depend on interrupt points.
Most use cases of fibers rely on them being easy and cheap to start up, and with low memory overheads. In TruffleRuby, fibers are currently implemented using operating system threads, so they have the same performance characteristics as Ruby threads. This will be addressed once the Loom project becomes stable and available in JVM releases.
MRI provides some classes that are described in the documentation as being available only on MRI (CRuby).
These classes are implemented if it is practical to do so, but this is not always the case. For example, RubyVM is not available.
Regexp instances are always immutable in TruffleRuby.
In CRuby 3.0, all literal Regexp are immutable, but non-literal are still mutable.
This limitation means that one cannot define singleton methods on a Regexp instance, and cannot create instances of subclasses of Regexp on TruffleRuby.
The -y, --yydebug, --dump=, and --debug-frozen-string-literal switches are ignored with a warning as they are unsupported development tools.
Programs passed in -e arguments with magic-comments must have an encoding that is UTF-8 or a subset of UTF-8, as the JVM has already decoded arguments by the time we get them.
The --jit option and the jit feature have no effect on TruffleRuby and warn. The GraalVM compiler is always used when available.
Ruby normally provides microsecond (millionths of a second) clock precision, but TruffleRuby is currently limited to millisecond (thousands of a second) precision.
This applies to Time.now and Process.clock_gettime(Process::CLOCK_REALTIME).
Ruby Strings are represented as a Java byte[].
The JVM enforces a maximum array size of 231-1 (by storing the size in a 32-bit signed int), and therefore Ruby Strings cannot be longer than 231-1 bytes.
That is, Strings must be smaller than 2GB. This is the same restriction as JRuby.
A possible workaround could be to use natively-allocated strings, but it would be a large effort to support every Ruby String operation on native strings.
Setting the process title (via $0 or Process.setproctitle in Ruby) is done as best-effort.
It may not work, or the title you try to set may be truncated.
If you use standard I/O streams provided by the Polyglot engine, via the experimental --polyglot-stdio option, reads and writes to file descriptors 0, 1, and 2 will be redirected to these streams.
That means that other I/O operations on these file descriptors, such as isatty, may not be relevant for where these streams actually end up, and operations like dup may lose the connection to the polyglot stream.
For example, if you $stdout.reopen, as some logging frameworks do, you will get the native standard-out, not the polyglot out.
Also, I/O buffer drains, writes on I/O objects with sync set, and write_nonblock will not retry the write on EAGAIN and EWOULDBLOCK, as the streams do not provide a way to detect this.
Error message strings will sometimes differ from MRI, as these are not generally covered by the Ruby Spec Suite or tests.
The set of signals that TruffleRuby can handle is different from MRI.
When using the native configuration, TruffleRuby allows trapping all the same signals that MRI does, as well as a few that MRI does not.
The only signals that can't be trapped are KILL, STOP, and VTALRM.
Consequently, any signal handling code that runs on MRI can run on TruffleRuby without modification in the native configuration.
However, when run on the JVM, TruffleRuby is unable to trap USR1 or QUIT, as these signals are reserved by the JVM.
In such a case trap(:USR1) {} will raise an ArgumentError.
Any code that relies on being able to trap those signals will need to fall back to another available signal.
Additionally, FPE, ILL, KILL, SEGV, STOP, and VTALRM cannot be trapped, but these signals are also unavailable on MRI.
When TruffleRuby is run as part of a polyglot application, any signals that are handled by another language become unavailable for TruffleRuby to trap.
TruffleRuby provides similar GC.stat statistics to MRI, but not all statistics are available, and some statistics may be approximations. Use GC.stat.keys to see which are provided with real or approximate values. Missing values will return 0.
Using most methods on ObjectSpace will temporarily lower the performance of your program.
Using them in test cases and other similar 'offline' operations is fine, but you probably do not want to use them in the inner loop of your production application.
Using set_trace_func will temporarily lower the performance of your program.
As with ObjectSpace, it is recommended that you do not use this in the inner loop of your production application.
Throwing exceptions and other operations which need to create a backtrace are slower than on MRI. This is because TruffleRuby needs to undo optimizations that have been applied to run your Ruby code fast in order to recreate the backtrace entries. It is not recommended to use exceptions for control flow on any implementation of Ruby anyway.
To help alleviate this problem, backtraces are automatically disabled in cases where we can detect that they will not be used.
Identifiers which are normally macros may be functions, functions may be macros, and global variables may be macros.
This may cause problems where they are used in a context which relies on a particular implementation (e.g., taking the
address of it, assigning to a function pointer variable, and using defined() to check if a macro exists).
These issues should all be considered bugs and be fixed.
Please report these cases.
rb_scan_args only supports up to 10 pointers.
rb_funcall only supports up to 15 arguments.
The mark functions of RDATA and RTYPEDDATA are not called during garbage collection, but called periodically.
The information about objects is cached as they are assigned to structs, and TruffleRuby periodically runs all mark functions when the cache has become full to represent those object relationships in a way that the garbage collector will
understand.
The process should behave identically to MRI.
TruffleRuby does not support the same interoperability interface to Java as JRuby does. TruffleRuby provides an alternate polyglot API for interoperating with multiple languages, including Java, instead.
Calling Ruby code from Java is supported by the GraalVM Polyglot API.
Using Java extensions written for JRuby is not supported.
Running TruffleRuby in the native configuration is mostly the same as running on the JVM. There are differences in resource management, as both VMs use different garbage collectors, but functionality-wise, they are essentially on par with one another.
Java interoperability works in the native configuration but requires more setup. By default, only some array classes are available in the image for Java interoperability. You can add more classes by compiling a native image including TruffleRuby. See here for more details.
"How many specs are there?" is not a question with an easy, precise answer. The number of specs varies for the different versions of the Ruby language, different platforms, and different versions of the specs. The specs for the standard library and C extension API are also very uneven and can give misleading results.
This blog post summarizes how many specs TruffleRuby passes.