summaryrefslogtreecommitdiff
path: root/include/ruby
diff options
context:
space:
mode:
authorJean Boussier <[email protected]>2025-06-13 17:56:26 +0200
committerJean Boussier <[email protected]>2025-06-13 23:50:30 +0200
commit15084fbc3c10d21769dd61cd1cd55b2662fa8845 ()
tree9f1e0011f56a9bef9aeb3139969e9b1e5217e00f /include/ruby
parent6dbe24fe5641e5c86638ff5c5d9fe08ea31d196d (diff)
Get rid of FL_EXIVAR
Now that the shape_id gives us all the same information, it's no longer needed.
Notes: Merged: https://.com/ruby/ruby/pull/13612
-rw-r--r--include/ruby/internal/fl_type.h35
1 files changed, 22 insertions, 13 deletions
@@ -253,6 +253,21 @@ ruby_fl_type {
= 0,
/**
* This flag has something to do with Ractor. Multiple Ractors run without
* protecting each other. Sharing an object among Ractors are basically
* dangerous, disabled by default. This flag is used to bypass that
@@ -286,18 +301,12 @@ ruby_fl_type {
*/
RUBY_FL_UNUSED9 = (1<<9),
- /**
- * This flag has something to do with instance variables. 3rd parties need
- * not know, but there are several ways to store an object's instance
- * variables. Objects with this flag use so-called "generic" backend
- * storage. This distinction is purely an implementation detail. People
- * need not be aware of this working behind-the-scene.
- *
- * @internal
- *
- * As of writing everything except ::RObject and RModule use this scheme.
- */
- RUBY_FL_EXIVAR = (1<<10),
/**
* This flag has something to do with data immutability. When this flag is
@@ -399,7 +408,7 @@ enum {
# pragma deprecated(RUBY_FL_DUPPED)
#endif
- = (int)RUBY_T_MASK | (int)RUBY_FL_EXIVAR
};
#undef RBIMPL_HAVE_ENUM_ATTRIBUTE