Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qualified ID enhance serialization format for human readability #7

Open
matanox opened this issue Dec 2, 2015 · 0 comments
Open

Qualified ID enhance serialization format for human readability #7

matanox opened this issue Dec 2, 2015 · 0 comments

Comments

@matanox
Copy link
Member

matanox commented Dec 2, 2015

A qualified ID type is currently used for giving symbols a unique name. It is composed of pairs of kind and name, e.g. (object, Foo). Sometimes extra pairs are also included such as in the case of function arguments - which are appended for function defs. Currently it is serialized using an ugly format that looks like (package|myPackage).(object|Foo).... It may be useful switching to a more smoothly humanly readable format, splitting into two strings, each more readable:

One string for just the names - e.g. package.Foo.apply.counter
One string for just the kinds - e.g. package.object.method.value

This will be more productive for diagnostics.

P.S. this means two separate fields rather than currently one, could be:

case class QualifiedID(nameConcatenation: SomeType, kindConcatenation: SomeType) {
  def ...
}
@matanox matanox changed the title Qualified ID serialization modification Qualified ID enhance serialization format for human readability Jan 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant