prefer is_bearable to isinstance

[rtbs-dev]

Ran into an issue with parametrized generics not being supported by isinstance. Since you're already relying on beartype, I've found it much easier to strictly rely on is_bearable to do dispatch, rather than isinstance. Stuff just behaves like I expect it to.

Line 389 in se.py was raising a SerdeError: isinstance() argument 2 cannot be a parametrized generic.

For more on the DOOR API see here, with is_bearable specifically documented here As it mentions there, this is designed to replace isinstance by being a strict superset:

is_bearable() is a strict superset of the isinstance() builtin. is_bearable() can thus be safely called wherever isinstance() is called with the same exact parameters in the same exact order:

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.50%. Comparing base (f1c49f2) to head (fe769df).
Report is 17 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #485   +/-   ##
=======================================
  Coverage   89.49%   89.50%           
=======================================
  Files          12       12           
  Lines        1933     1934    +1     
  Branches      401      401           
=======================================
+ Hits         1730     1731    +1     
  Misses        148      148           
  Partials       55       55           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yukinarit]

LGTM