Note the "Unit" used as the key for the Uint, type. This may or may not impact the code generation, but this needs to be investigated and fixed, if a problem. There is a chance that there is no impact, as the types in this map, are sequentially iterated as opposed to be directly accessed via the key. (... which begs the question, why isnt it an array instead of a map!)
"Unit" = [PSCustomObject]@{
TypeName = "Uint"
GoType = "uint"
FlagName = "Count"
Short = "c"
Def = "uint(0)"
Setup = "paramSet.Native.Count = {{OPTION-VALUE}}"
Assert = "Expect(value).To(Equal({{OPTION-VALUE}}))"
Equate = "Equal"
Validatable = $true
OptionValue = "99999"
#
PsTcEntry = [PSCustomObject]@{}
GenerateSlice = $true
SliceFlagName = "Counts"
SliceShort = "P"
DefSliceVal = "[]uint{}"
ExpectSlice = "[]uint{2, 4, 6, 8}"
SliceValue = "2,4,6,8"
#
Comparable = $true
Containable = $true
#
BhParent = "Int"
CastLiteralsAs = "uint"
#
BhTests = $null
}
Note the "Unit" used as the key for the Uint, type. This may or may not impact the code generation, but this needs to be investigated and fixed, if a problem. There is a chance that there is no impact, as the types in this map, are sequentially iterated as opposed to be directly accessed via the key. (... which begs the question, why isnt it an array instead of a map!)