in 0.4, is Symbol( "foobar" ) canonical?

[tonyhffong]

In light of #8712, both of these work:

symbol( "foobar" )
Symbol( "foobar" )

do we have a recommendation which one users should stick to?

[tonyhffong]

I guess it's the same question for UInt and Int.

[tkelman]

#1470 (comment)

Do we start deprecating at least some of the lower-case conversion functions now?

[ivarne]

Those deprecations will be annoying for those who writes 0.3 - 0.4-dev compatible packages. I'd suggest we add those when we start preparing for the 0.4.0 release.

[tonyhffong]

Sounds like we do want to nudge users toward the camelcase versions, but not too harshly until 0.4.0 release. Am I understanding it correctly?

[tonyhffong]

Also sounds like this is a dup. Closing.

[ivarne]

A dup of what? Even if everybody agrees that symbol(), int(), and so on, should be deprecated, it is an outstanding issue to actually deprecate them. (I just don't think it is a hurry, because compatibility is a major hassle and fixing the issue is a really quick search and replace.)

[tonyhffong]

A dup of #1470, as @tkelman pointed out. It seems to be the issue to follow on this topic.

[ivarne]

Sorry, I somehow believed #1470 was closed.