Idiomaticy of using Option<> as a function argument

Hey rusty people,

Is there any reason to avoid using Option<> to represent an optional function argument? It seems useful in many cases, but a lot of libraries seem to prefer two separate functions (frequently one adds a default then calls the other). Just wondering if any guidelines or reasoning for this exist, outside of perhaps some (debatable) clarity.