I'm developing an interface in which it makes sense that objects are stored in
Arcs. All the functions take in
Arc<Blah> types. But it is conceivable - at least in theory - that someone, somewhere, would want to .. not use
Arcs, so the
new() methods don't actually return
Arcs. But now that I'm actually using the API myself I'm getting somewhat frustrated by having to sprinkle
Arc::new() everywhere, and I'm thinking about making all
However, I tend to think like this: Have I ever seen this done before? No? Well is there perhaps a good reason I have never seen this done before?
Do you feel it is anti-social to return
Arc-wrapped objects from
new() methods? Would you prefer to
Arcify yourself, even though it becomes quite verbose?
It's possible to unwrap an
Arcd object, as long as the count is 1, if I recall correctly -- so it wouldn't be a huge burden if one were so inclined.