Skip to content
This repository has been archived by the owner on May 11, 2019. It is now read-only.

RFC: Unicode Support #11

Open
Qix- opened this issue May 31, 2016 · 6 comments
Open

RFC: Unicode Support #11

Qix- opened this issue May 31, 2016 · 6 comments
Labels
Projects

Comments

@Qix-
Copy link
Owner

Qix- commented May 31, 2016

TODO

@Qix- Qix- changed the title RFC: UTF-8 RFC: Unicode Support May 31, 2016
@corbin-r
Copy link

corbin-r commented Jun 4, 2016

As a question, I'm assuming when you say unicode support you mean UTF-8? As there are several UTF formats, UTF-8 being the most common.

@Qix-
Copy link
Owner Author

Qix- commented Jun 4, 2016

UTF-8, UTF-16, UTF-32 and UTF-64.

typedef [u8] as str8
typedef [u16] as str16
typedef [u32] as str32
typedef [u64] as str64

alias str8 as str

@corbin-r
Copy link

corbin-r commented Jun 4, 2016

@Qix-
Sweet. That certainly will be nice, having full UTF8-64 support.

@Qix-
Copy link
Owner Author

Qix- commented Jun 4, 2016

@PolyGN yep see the updated #3 for why the typedef and alias keywords are how they are in the above comment.

@corbin-r
Copy link

corbin-r commented Jun 4, 2016

@Qix- ahhh I see. So alias "renames" but without the copy of the original type, typedef copies the original type and renames. I quite like that because using alias could save bit space where needed.

@Qix-
Copy link
Owner Author

Qix- commented Jun 4, 2016

typedef creates a new type out of an existing type. alias just creates an alias for a type.

You can think of it like this:

typedef Foo as Bar
class Bar : private Foo {};

and

alias Foo as Bar
#define Bar Foo

@Qix- Qix- added the todo label Jun 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
RFCs
Proposed
Development

No branches or pull requests

2 participants