You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The old API allowed for named threads. They didn't do anything functionally except identify which thread was doing what in warning messages. Ideally, if we did allow for this, we could keep a cache and access the different threads by name. That might be useful.
However, I won't bother with this feature unless there is sufficient demand for it.
Note, because of the changed API it will likely have to be an option rather than an argument of the #autoreload method, e.g.
autoreload('foo.rb', :name=>:foo)
The text was updated successfully, but these errors were encountered:
The old API allowed for named threads. They didn't do anything functionally except identify which thread was doing what in warning messages. Ideally, if we did allow for this, we could keep a cache and access the different threads by name. That might be useful.
However, I won't bother with this feature unless there is sufficient demand for it.
Note, because of the changed API it will likely have to be an option rather than an argument of the #autoreload method, e.g.
The text was updated successfully, but these errors were encountered: