Closed tjpalmer closed 10 months ago
In TmpLTranslator, the Date type definition has all these in be-csharp:
_members = {ArrayList@6631} size = 6
0 = {TmpL$InstanceProperty@6638} @docString(["The year. 1900 means 1900.", "The year. 1900 means 1900.", "std//temporal.temper.md"]) let year__34: Int;
1 = {TmpL$InstanceProperty@6639} @docString(["The month of the year in [1, 12].", "The month of the year in [1, 12].", "std//temporal.temper.md"]) let month__35: Int;
2 = {TmpL$InstanceProperty@6640} @docString(["The day of the month in [1, 31]\nadditionally constrained by the length of [month].", "The day of the month in [1, 31]\nadditionally constrained by the length of [month].", "std//temporal.temper.md"]) let day__36: Int;
3 = {TmpL$Getter@6641} get.year -> getyear__53(this = this__54, this__54: System.DateTime): Int {return /* this */ this__54.year__34;}
4 = {TmpL$Getter@6642} get.month -> getmonth__57(this = this__58, this__58: System.DateTime): Int {return /* this */ this__58.month__35;}
5 = {TmpL$Getter@6643} get.day -> getday__61(this = this__62, this__62: System.DateTime): Int {return /* this */ this__62.day__36;}
But it only has the instance properties in be-py.
I have no idea yet why it would be different between the two.
I think it's because I don't connect the getters. And I don't because default rendering is fine for C#. But then it's confusing the part that figures out if the definitions of those getters is needed. I guess I'll connect them to simple member getters after all.
Completed in a recent PR.
We're building a std Date class for C#:
It also causes some warnings from the C# compiler:
But I don't see the class generated for other backends, so there's probably some way to avoid it.