How UTF-8 Works

Re:How UTF-8 Works by morelisp on Wednesday February 09, 2022 @07:02AM (#30271669)

A type system can refuse to turn a `bytes` into a `utf8str` until it's been appropriately parsed.

(It doesn't even need to be a very good or strongly-enforced type system - Go makes it dangerously easy to convert between `[]byte` and `string` by other-type-system standards, and yet everything works pretty well. It's enough to hitch your thinking and make you realize you need another step.)

[ Parent | on HN ]

Re:How UTF-8 Works by BiteCode_dev on Wednesday February 09, 2022 @09:01AM (#30272686)

How does the type system knows the bytes are utf8 and not CP850?

[ Parent | on HN ]

Re:How UTF-8 Works by morelisp on Wednesday February 09, 2022 @11:39AM (#30274715)

The same way you can parse a string into an integer and it knows you got an either[integer, err].

[ Parent | on HN ]

Re:How UTF-8 Works by BiteCode_dev on Wednesday February 09, 2022 @12:04PM (#30275008)

So it doesn't, and it's not about the type system. Any decode operation in python 3 raise an exception or return string.

It's about the runtime error handling making it mandatory to deal with the error and won't let you panic at run time for this specific error.

[ Parent | on HN ]

Re:How UTF-8 Works by morelisp on Wednesday February 09, 2022 @12:07PM (#30275050)

I'm sorry you don't see exceptions as part of a type system yet.

[ Parent | on HN ]