Thread overview | ||||||
---|---|---|---|---|---|---|
|
May 23, 2019 [Issue 19896] [internals] Represent string and arrays as sparse literals | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19896 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ibuclaw@gdcproject.org -- |
May 25, 2019 [Issue 19896] [internals] Represent string and arrays as sparse literals | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19896 Nicholas Wilson <iamthewilsonator@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iamthewilsonator@hotmail.co | |m --- Comment #1 from Nicholas Wilson <iamthewilsonator@hotmail.com> --- I think we should be fast and memory efficient for the common case, and most string aren't sparse. What use case is that? -- |
June 10, 2019 [Issue 19896] [internals] Represent string and arrays as sparse literals | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19896 --- Comment #2 from Iain Buclaw <ibuclaw@gdcproject.org> --- (In reply to Nicholas Wilson from comment #1) > I think we should be fast and memory efficient for the common case, and most string aren't sparse. What use case is that? I'm willing to admit that StringExp may be the wrong target to try to fix. ArrayLiteralExp's however I won't give up on. Casting a StringExp to any array type shouldn't create a new (potentially bigger) StringExp. -- |
December 17, 2022 [Issue 19896] [internals] Represent string and arrays as sparse literals | ||||
---|---|---|---|---|
| ||||
https://issues.dlang.org/show_bug.cgi?id=19896 Iain Buclaw <ibuclaw@gdcproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P3 -- |
Copyright © 1999-2021 by the D Language Foundation