There's no form of inheritance currently supported, no.
The problem with inheritance that at least in the naive case (where you'd copy all fields from base class to derived) you'd have to freeze the base class, since adding any fields to the base class would shift all fields in the derived class, which is an incompatible change. You can of course assign explicit field ids, and make sure you start ids for derived tables with "some room" from the base, but this is clumsy too.
A more robust way to make a derived table is to simply have an instance of the base be the first field of the derived, though of course that doesn't make them compatible/polymorphic. One thing we could consider is to officially support this pattern by generating accessor methods on the derived table that can indirect to the base table, but that doesn't sound super helpful/efficient either.