I’m trying to learn a little more about D’s compile time evaluation and understand how its templates, mixins, attributes, etc all work. One thing I’d like to try and do is figure out an elegant way to mark a class’s members as being serializable or loadable from a database. In the example below, I’ve created a tuple that lists which members to use when reading or (later on) serializing the instance.
My first question is, is this a proper usage of tuples as it stands below? And secondly, if so, is there a way to generate this tuple automatically at compile time using the user defined attributes I’ve assigned to the relevant member variables? I’ve dug through the various documentation pages like http://dlang.org/attribute.html and http://dlang.org/phobos/std_traits.html but I can’t seem to figure out how to use them properly for this purpose (i.e. looping through a class’s members and determining which variables have the desired attribute). I’m also not quite certain if I have completely the wrong idea about how attributes are supposed to be used. Any suggestions on the best way to go about this would be appreciated.
enum ENCODABLE = 1;
alias string[string] Row;
template Tuple (T...) { alias T Tuple; }
class A {
@(ENCODABLE) string name;
@(ENCODABLE) int x;
int* p;
alias Tuple!("name","x") encodables;
this(Row row) {
foreach (var; encodables) {
__traits(getMember, this, var) = to!(typeof(__traits(getMember, this, var)))(row[var]);
}
}
}
void main() {
Row row = ["name":"Asdf", "x":"120"]; // Simulated database row
auto a = new A(row);
writefln("%s,%d,%d", a.name, a.x, a.p); // Asdf,120,null
}
I’ve managed to get it working with the following code, and a little help from the isValueInTuple template based on code provided in CyberShadow’s answer. It still feels a bit clunky, but seems to get the job done. Comments/criticism welcome if I’m doing something horrible against the nature of templates!