Future features for class Atomic

[jeanmathieupotvin]

I/O

It could be nice to simplify the I/O interface of the class with just two methods $read() and $write().

$write()

• Could gain a simple format = c("yaml", "json") argument that would call private methods $as_yaml() and $as_json().
• Argument file should not need a file extension as it is the case right now. It should simply be a file name. The file extension would be automatically appended by argument format.

$read()

• It's cool to be able to share blueprints representations with $write(), but we need a way to read them back. This $read() method would need to assemble back a Blueprint object from its text representation.
• Maybe we could add a way to serialize these objects?

[jeanmathieupotvin]

Revamp and simplify new() ?

It could be a good idead to simplify the constructor method $new(). Instead of having to write $new(double(), "test", 1L) (as an example), we could simplify the raw constructor and write $new("double", "test", 1L) instead. Why? Because the first behavior is already handled by the Blueprinter.

It has advantages: speed, code optimization, more features / choices for users. But it also has a big disadvantage: it breaks most of unit tests and requires a dev version of its own.