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 seems now that the hamcrest.hrl file is only generated to have all the matchers auto-imported.
Would you accept a pull-request for making that header static or for replacing the ?assertThat macros with functions that could be instrumented using parse-transform?
Use of the parse-transform would allow to avoid including the header into the user code at all. I think that could be implemented similarly, as it is done in the lager application.
The text was updated successfully, but these errors were encountered:
It seems now that the
hamcrest.hrl
file is only generated to have all the matchers auto-imported.Would you accept a pull-request for making that header static or for replacing the ?assertThat macros with functions that could be instrumented using parse-transform?
Use of the parse-transform would allow to avoid including the header into the user code at all. I think that could be implemented similarly, as it is done in the
lager
application.The text was updated successfully, but these errors were encountered: