[ 
https://issues.apache.org/jira/browse/SLING-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793692#action_12793692
 ] 

Michael Dürig commented on SLING-1236:
--------------------------------------

Chained implicits: I have taken a closer look at this. The implicits are not 
really chained in the sense which is excluded by the language spec. Rather do 
they cascade their views which is why the given example works. 

I tried to apply the technique to the Scala scripting engine such arguments 
passed to the script become eligible for implicit conversion again. This only 
works in the most simple case however. In other cases this produces lots of 
ambiguities between different implicit conversions. 



> Scala Scripting: Make all types of the script arguments visible on the Scala 
> side
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-1236
>                 URL: https://issues.apache.org/jira/browse/SLING-1236
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Michael Dürig
>            Priority: Minor
>         Attachments: SLING-1236.patch
>
>
> Currently the Scala scripting engine inserts a preamble for the bindings 
> passed to a Script. The preamble contains a declaration of the following form 
> for each value in the Bindings instance:
>   val request: SlingHttpServletRequest = 
> bindings.get("request").asInstanceOf[SlingHttpServletRequest]
> The types are hard coded in the ScalaScriptEngine.TypeHints class. For 
> unknown types a declaration of type AnyRef is inserted into the preamble. 
> I suggest to implement a run time type discovery algorithm which discovers 
> the accessible type from a given instance and inserts the respective 
> declarations into the preamble. That way the static coupling between the 
> known values in Bindings and its types would go away. Furthermore the values 
> would be of a type appearing to be of all the visible types on the Scala side.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to