Timeline for Rectangle Class
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2020 at 13:24 | history | edited | Community Bot |
Commonmark migration
|
|
| May 23, 2017 at 12:41 | history | edited | Community Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Feb 19, 2017 at 14:31 | comment | added | Trauer | Because I thought that the system's one "bottom" and "right" were stored, like JanDotNet suggested me to do. And I actually did copy Microsoft's GetHashCode implementation. I'll edit the questions to explain why I implement IEnumerable. | |
| Feb 19, 2017 at 9:27 | history | edited | t3chb0t | CC BY-SA 3.0 |
added 461 characters in body
|
| Feb 19, 2017 at 8:07 | history | edited | t3chb0t | CC BY-SA 3.0 |
added 1407 characters in body
|
| Feb 19, 2017 at 5:59 | comment | added | t3chb0t | @Trauer it has a smaller memory foot print this makes me curious. Could you explain why because when I look at the source code of the system rectangle they use for fields and you use four fields, the only difference is that your fields are readonly, everything else is exactly the same. Sometimes it looks like you have just copy/pasted their code, renamed the variables and made them readonly ;-] I'm also curious why you need it to be enumerable. | |
| Feb 19, 2017 at 4:55 | comment | added | Trauer | Indeed, my library can work with this one (and doesn't work with this system's one). Besides immutability it has a smaller memory foot print. Implementing IEnumerable is kinda weird... It does have it's uses... But it's far too pythonic for a C# project, I think... | |
| Feb 18, 2017 at 21:53 | history | answered | t3chb0t | CC BY-SA 3.0 |