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
It would be easier and I don't have to explictly import Flux and just specify :relu because I coming to MLJFlux because I am not interested in using or importing Flux.
Possible Implementation
Something like:
functionget_activation(func_symbol::Symbol)
ifhasproperty(Flux, func_symbol)
returngetproperty(Flux, func_symbol)
elseerror("Function $func_symbol not found in Flux.")
endend
The text was updated successfully, but these errors were encountered:
I think to keep things simple we either re-export the entire Flux namespace, or we re-export none of it. I think the latter and current choice gives the user more control, and it's not too burdensome to run using Flux to get dircect access to Flux's exported methods.
In case it was not clear to you, after using Flux you can do relu, Dense, etc without the Flux. qualification.
In docs we always try to put in the Flux. qualifier, because we cannot assume the user has done using Flux.
Even if we did re-export Flux's namespace, it won't help if the user never runs using MLJFlux, which they can indeed avoid with @load NeuralNetworkClassifier or similar, for that macro only does import MLJFlux.
My vote would be for the status quo. Anyone else prefer we re-export the Flux namespace?
Motivation and description
It would be easier and I don't have to explictly import
Flux
and just specify:relu
because I coming toMLJFlux
because I am not interested in using or importingFlux
.Possible Implementation
Something like:
The text was updated successfully, but these errors were encountered: