How COString should internally store characters

Registered by tiwake

After talking with a few people, COString should use type char[] for storage and manipulation of chars. Reason being is that a linked list would take much longer to iterate through and would use much more memory. Destroying a char[] and making a new, bigger one would be slightly slower for inserting chars, but is not worth it.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.