# Can you avoid using Base.invokelatest in this example?

**URL:** <https://discourse.julialang.org/t/can-you-avoid-using-base-invokelatest-in-this-example/33269>\
**Category:** General Usage\
**Created:** [January 12, 2020, 4:47pm UTC](https://discourse.julialang.org/t/can-you-avoid-using-base-invokelatest-in-this-example/33269 "2020-01-12T16:47:09Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [January 13, 2020, 12:21pm UTC](https://discourse.julialang.org/t/can-you-avoid-using-base-invokelatest-in-this-example/33269/16 "2020-01-13T12:21:12Z")

</div>

> [@rvignolo](#):
>
> Yes, I am aware of that. I am doing this because I don’t want the user of my library to write functions but instead, write a really simple input using macros. Then, I use the expressions provided in the macros to build functions. That’s it.

If you are using macros, then you shouldn’t need `eval` or `invokelatest`. Macros can build a function expression that is handled at compile time, not runtime.

Could you give an example of the type of syntax you are trying to achieve?

---

_[View the full topic](https://discourse.julialang.org/t/can-you-avoid-using-base-invokelatest-in-this-example/33269)._
