Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>One of the things you're seeing is that Scala is, above all, a strongly-typed functional language <em>on the JVM</em></p> <p>Scala is not <em>just</em> a Functional language. It did start off as one (Funnel: <a href="http://lamp.epfl.ch/funnel/" rel="nofollow noreferrer">http://lamp.epfl.ch/funnel/</a>), but this was then extended to make it an Object-Oriented language, with the explicit goal of making it strongly interoperable with Java classes.</p> <p>abstraction and overriding and packages are all examples of this interoperability in action.</p> <hr> <p>The remainder might be considered not as new features, but simply as removing restrictions from Java. Taking them one at a time:</p> <p><strong>traits and object hierarchy linearization</strong></p> <p>Removes the restriction that Java interfaces can only contain abstract methods. Linearisation is how Scala resolves the diamond-inheritance problems that this would otherwise cause.</p> <p><strong>singletons</strong></p> <p>Java static methods are a hangover from it's C++ syntax heritage, which in turn added them to better support the procedural style need for interop with C. Static methods are very much NOT object oriented (see this question: <a href="https://stackoverflow.com/questions/4112088/why-are-singleton-objects-more-object-orientated/4112864#4112864">Why are singleton objects more object-oriented?</a>)</p> <p><strong>companion objects</strong></p> <p>Allow singletons to be used in lieu of static methods, with their privileged access rights. </p> <p><strong>implicit conversions</strong></p> <p>Java already does this, but it's restricted to only implicitly converting objects and primitives to strings, as in the expression <code>"" + 3</code>. Scala just extends this idea and allows the programmer to use it for other conversions.</p>
    singulars
    1. This table or related slice is empty.
    1. POEfficacy of sticking to just the functional paradigm in Scala
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USKevin Wright
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI thinks that there is a bit more to implicits than *conversions*; there are also the implicit *parameters* which, together with scala's type system, allow libraries like scalaz to do so much cool, functional stuff
      singulars
      1. PO
      1. USoxbow_lakes
    2. COOh, absolutely there's a lot more to implicits. I was just addressing the specific mention of "implicit *conversions*" in the original question :)
      singulars
      1. PO
      1. USKevin Wright
    3. COI was being picky - I know full well that you know about this stuff `:-)`
      singulars
      1. PO
      1. USoxbow_lakes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload