# How to determine the methods for a callable object without instantiating it?

**URL:** <https://discourse.julialang.org/t/how-to-determine-the-methods-for-a-callable-object-without-instantiating-it/102618>\
**Category:** General Usage\
**Created:** [August 8, 2023, 10:58pm UTC](https://discourse.julialang.org/t/how-to-determine-the-methods-for-a-callable-object-without-instantiating-it/102618 "2023-08-08T22:58:26Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![algunion](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/algunion/32/51630_2.png) [@algunion](https://discourse.julialang.org/u/algunion)\
**Post date:** [August 14, 2023, 12:12pm UTC](https://discourse.julialang.org/t/how-to-determine-the-methods-for-a-callable-object-without-instantiating-it/102618/18 "2023-08-14T12:12:59Z")

</div>

@Benny , thank you for the insights.

I’ll not be able to put much work into this in the following days - but before updating that PR, I would really like to somehow _validate_ this (and your idea of a standalone package where we can iterate fast seems attractive indeed).

I wrote **[this](https://discourse.julialang.org/t/community-driven-juliapowerpack-patching-pains-and-incubating-new-ideas/101988)** a while back - and this was the exact rationale: to have a fast-moving environment where we can iterate/validate ideas. Also, don’t wait for the slow-paced review process (and this is not a critique - I just admit the existing/expected constraints) before making valuable stuff available to the community.

I might revisit [that](https://discourse.julialang.org/t/community-driven-juliapowerpack-patching-pains-and-incubating-new-ideas/101988) idea.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-determine-the-methods-for-a-callable-object-without-instantiating-it/102618)._