2017-02-02 12:55:50 -0600 | commented question | Private members in TypeDepth class Sure thing. I was going to originally, but since it's not really an issue I decided to use the Q&A forum first. I wouldn't go as far as removing it, since I do see a use for it. |
2017-02-01 19:15:08 -0600 | received badge | ● Student (source) |
2017-02-01 17:42:01 -0600 | commented question | Private members in TypeDepth class Based on your tips I managed to reduce my implementation to something a lot more pleasant. Thanks! Now back to the original topic, those TypeDepth traits are useless for the time being. |
2017-02-01 15:52:53 -0600 | commented question | Private members in TypeDepth class Added the use case. |
2017-02-01 15:52:01 -0600 | received badge | ● Editor (source) |
2017-02-01 13:33:17 -0600 | asked a question | Private members in TypeDepth class This is more a question for the developer/contributor team. I was looking for methods to infer the native type automatically based on the depth value and came across the Any particular reasons for this? e.g.: it's implementation/architecture dependent and therefore cannot be used reliably, something of that sort. If there's no actual reason, could you expose the members in the next releases? Edit: Intended use case I wanted to generate a colormap representation for a matrix of type Below is an initial version of what was going to be my implementation. Cheers |