sorbet-runtime 0.4.4346 → 0.4.4347

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 2b1e8c1fd45fe06fefe7d3f963844361ce24611e
-  data.tar.gz: d7ee0c4b805680c5f5da04a45276b0583139a634
+  metadata.gz: 5fb5d2b28ef8ba9e3da543ec36508c787129dde4
+  data.tar.gz: 9ab0133e5ab9652fcd839462fd975101f6b02412
 SHA512:
-  metadata.gz: ed2b3353f16be3732c4ee26a98bfddd6e451620d6b2d061ea021d35ab4e0163d6701b2c062cf39b5e624814ad1128ee5f45e9152cbbfcd3d04d71e40dd1e0e03
-  data.tar.gz: 16f9c1d5468429c3ebeadce07fd63b3568fde1a707b172fd632ece82faafd7623b8a4736a207bfd43651f68fa9b0781f2b754d7036f8a38c5c969b2229759860
+  metadata.gz: c52e070829b42091dcbe13c22ecca0d6bafd70c5b838855b0994f71ce93ca3a1463f1f704755d09c73443e4ea865fa378aaac0e7d68192b554cb68d8aa32540b
+  data.tar.gz: '058b90d8a1c4ca8ef9c8aff3bf9836dd02da977d2899d9a9ee1e1b5ba1b1a1679534bce9eec37cabf0cb36dde0b7dac0ffa8c92208300f7d9f6d4811091ca5dd'

data/lib/types/private/methods/decl_builder.rb

@@ -131,9 +131,6 @@ module T::Private::Methods
     end
 
     def generated
-      if T.unsafe(true)
-        raise "The .generated API is unstable, so we don't want it used until we redesign it. To change Sorbet's runtime behavior, see https://sorbet.org/docs/tconfiguration"
-      end
       check_live!
 
       if !decl.generated.equal?(ARG_NOT_PROVIDED)

data/lib/types/runtime_profiled.rb

@@ -2,35 +2,23 @@
 # frozen_string_literal: true
 
 #
-# Hey there!
+# From the static system, T::Utils::RuntimeProfiled is T.untyped.
 #
-# T::Utils::Runtime is just a random class. Chances are[^1] it's not a class
-# that your variables are instances of, which means that using it in a type
-# signature will always create a type error.
+# But from the runtime system, it's a random class (specifically, a class that
+# normal programs currently don't have any instances of).
 #
-# At first, it doesn't seem like a good thing to have a type that's sole
-# purpose is to cause type errors. The trick is that within the ruby-types
-# team, we only use T::Utils::RuntimeProfiled within 'generated' sigs.
+# Thus, T::Utils::RuntimeProfiled can be used to introduce runtime-only type
+# errors. This seems like a bad idea, but it's not. It can be used to gather
+# runtime type information from running code via a custom T::Configuration
+# handler.
 #
-# Unlike normal sigs, generated sigs never raise at runtime. They also log the
-# actual, observed type on type error to a central location. We're using these
-# observed types to refine and expand our type coverage in pay-server.
+# This process has only ever been used at Stripe, and is likely to have rough
+# edges. If you've managed to find your way here and you're curious to try it,
+# please chat with us on Slack. There are no docs.
 #
-# What does this all mean for you?
-#
-# - If you were just curious, that's it! Leave the sig as is, and carry on.
-# - If you wanted to replace this sig with a better, hand-authored one:
-#
-#   1. Remove 'generated' from the sig.
-#   2. Update the sig to your liking
-#
-# Questions? :portal-to: => #ruby-types
-#
-# [^1]: Unless you happen to be calling T::Utils::RuntimeProfiled.new directly...
+# See also: the --suggest-runtime-profiled flag to sorbet.
 #
 
 module T; end
 module T::Utils; end
-# Sorbet guesses this type instead of T.untyped when passed --suggest-runtime-profiled
-
 class T::Utils::RuntimeProfiled; end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: sorbet-runtime
 version: !ruby/object:Gem::Version
-  version: 0.4.4346
+  version: 0.4.4347
 platform: ruby
 authors:
 - Stripe