Hi, I'm having a weird issue where I only call (st/instrument) in my code and aim to instrument only the used functions in my code base

but somehow it seems to begin to generate arguments for some of the functions in the codebase

If I'm only aiming to instrument my code, I shouldn't need clojure.test.check and its submodules, right?

somehow when I run my program it whines those need to be required.. then when I add them it begins to generate inputs and all hell breaks loose

@theamazingekko do you by any chance use s/fspec ?

and yes, I do use s/fspec

oh boy do I use it!

so okay.. I'm starting to get a picture here

so it is possible that instrumentation may attempt to generate arguments for arguments that are functions in some cases?

if theres HOFs

hmm... so if this is a problem I need to maybe simplify those specs.. maybe by using ifn? instead of full-fledged f/spec

are there any other workarounds.. in a way I'd like to keep that stricter form so I could then run generative tests separately later on

can I be a total pig and set clojure.spec.alpha/*fspec-iterations* to 0 😄 😄 😄

yes, I think this is an "interesting" feature of spec

yeah it seems that just restricting the iterations solved my issues for now

thanks! I've been stuck with this over a day 😄

basically it was just about finding a right config.. it's very "interesting" indeed