Squeal should use non-generic class name about squeal HOT 7 CLOSED

Hey Christopher!

Swift types are namespaced by their module names. The full name of the class is actually Squeal.Database, but the compiler only requires the namespace when there is a conflict.

But if you really hate the name, you can always create a typealias:

typealias SquealDB = Squeal.Database
var db = SquealDB()

Does this calm your cringes? After years of having to prefix classes with XYZ (due to the lack of namespaces), I'm pretty happy to not have the name of my project in my class names anymore.

from squeal.

The things I was reading about the automatic namespacing behaviour seemed to indicate that it was a minefield, but if I can personally just use Squeal.Database where others might conceivably just use Database I suppose that'll be just fine.

It seems obvious now that the problem isn't that your class isn't namespaced, it's that the namespacing is, depending on your perspective, either all loosey goosey or groovily transparent. From my Ruby background I'm definitely going with the former :-D

Thanks for the quick feedback!

from squeal.

No problem!

Out of curiosity, where have you been reading about issues with automatic namespacing? I know that at the LLVM layer, modules don't deal with collisions. Objective-C modules, for example, don't prevent collisions. But I thought that the Swift compiler does force authors to deal with collisions.

from squeal.

I personally haven't had problems, simply because I'm so very very very new to Swift. My thought process was as follows: (1) I want to use SQLIte (2) Few minutes of googling later, I find Squeal. Awesome. (3) Bang my head against the wall for a few hours trying to write the most basic of classe and most trivial of tests (4) Take a break to look at the Squeal API (5) See that the entry point is just a "Database" class. (6) Google around for swift and namespacing, find only woe and gnashing of teeth (7) Complain about class name (8) Discover that explicit namespacing is optional, and curse the language gods

from squeal.

I must be dumber than a two year old because I'm getting "No such module 'Squeal'" if I import Squeal and "Use of undeclared type 'Squeal'" if I don't. I'm starting to regret giving iPhone dev another try.

from squeal.

I think you're running into the same issue in #14. The long and short: you need to ensure your app is linked against the Squeal framework. I should've updated the docs sooner :/

iOS development definitely has a steeper initial learning curve, especially if you're coming from a completely different toolset. But once you get yourself oriented there's a lot of great things to build and enjoy.

from squeal.

I did iOS dev for a year back in 2011/2012 and as long as I could stay in the code and the APIs I was golden. The moment I had to do anything in xcode... oy.

Hallelujiah adding the framework did the trick. Well, for that problem at least :P

from squeal.