Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>scalap to the rescue!</p> <p>I took this code:</p> <pre><code>object TestThing extends App { def one { println("one") } def two[T] { println("two") } def three[T : Manifest] { println("three") } def four[T: Manifest, U : Manifest] { println("four") } } </code></pre> <p>and ran it through scalap. Here's what I got:</p> <pre><code>object TestThing extends java.lang.Object with scala.App with scala.ScalaObject { def this() = { /* compiled code */ } def one : scala.Unit = { /* compiled code */ } def two[T] : scala.Unit = { /* compiled code */ } def three[T](implicit evidence$1 : scala.Predef.Manifest[T]) : scala.Unit = { /* compiled code */ } def four[T, U](implicit evidence$2 : scala.Predef.Manifest[T], evidence$3 : scala.Predef.Manifest[U]) : scala.Unit = { /* compiled code */ } } </code></pre> <p>As you can see, the first implicit Manifest is called <code>evidence$1</code>. The second and third—<strong>though in a different scope!</strong>—are called <code>evidence$2</code> and <code>evidence$3</code>. So... that's how you make reference to Manifests.</p> <p>Despite that, though, it seems a bit scary to me that removing a Manifest that is higher up in the class will change the name of a Manifest that is located lower in the file. Similarly, it also doesn't help that the IntelliJ Scala plugin's syntax highlighting seems to think that the Manifest variables in scope in <code>four()</code> are <code>evidence$1</code> and <code>evidence$2</code>, and it doesn't think that <code>evidence$3</code> is a valid variable there (even though it is, and <code>evidence$1</code> is not). Overall, maybe these things should be heeded as warning signs about playing with implicit Manifest variables?</p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I access implicit "implicit" i.e. def a[A :B] or def a[A <% B]?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDestin
    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. VTDownMod
    1. COSurely those names should be an internal implementation detail and not relied on!
      singulars
      1. PO
      1. USBen
    2. CO@Ben You'll get no opposition from me there....
      singulars
      1. PO
      1. USDestin
    3. COThat is why you use `implicitly`... trying to use `evidence$1` etc in your code won't compile.
      singulars
      1. PO
      1. USLuigi Plinge
 

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