-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reactant compatibility #15
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #15 +/- ##
=====================================
Coverage 0.00% 0.00%
=====================================
Files 5 6 +1
Lines 299 288 -11
=====================================
+ Misses 299 288 -11 ☔ View full report in Codecov by Sentry. |
Nice. Can you split out a "General type stability/code improvements" PR that we can merge right away (maybe after some timing tests), and try the reactant stuff on top of that? |
This PR ended up being more of a general refactor, moving away from the style of original Python implementations to a more type-stable Julian setup, which should be compatible with Reactant, but that is not stable yet. |
There should be no breaking changes. Layer types have been given type parameters for type stability and compilability. Layer types are also now exported.
Compiling with Reactant
TransformerBlock
This seems to work fine
Transformer
This fails for some reason:
Buuut.... it's not an implementation thing:
So probably has to do with the fields or type parameters? My bet is the transformer blocks, which is currently a
AbstractVector{<:TransformerBlock}
. We might opt for using an NTuple or Chain.