Improvement Request on Highlighting Implicit Conversions - Scala IDE User

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Improvement Request on Highlighting Implicit Conversions
Received-SPF: pass (google.com: domain of ja...@banshee.com designates 209.85.217.175 as permitted sender) client-ip=209.85.217.175;
MIME-Version: 1.0
In-Reply-To: <D445BA47-E08B-49CC-A135-EDC759C59...@typesafe.com>
References: <CADVSO_h41-+PC1zccxdC4O76cnEmSi0SebyPVoRdSBJd6m5...@mail.gmail.com>
 <6e3f4c2c-0b83-4a8a-a3c6-93732f4dd...@p5g2000vbl.googlegroups.com>
 <CAAtns_CuH5tUFQY4R9gioLgG3xMkLuAbNvvbxRfkuXBcNnZ...@mail.gmail.com>
 <4946FD1C-A54B-4AE6-8672-B46DA07E9...@typesafe.com> <CAAtns_BBsASNNRuK485MAkj_8Gq05NaEHg3qHUnb=LoHYQ=...@mail.gmail.com>
 <CAAtns_DmPOszCJX3CgeEHMn1Q4pTWibBZWY5rV+evYSoV8N...@mail.gmail.com>
 <045aa5cd-2d10-473d-a3a9-63b6a568b75f@googlegroups.com> <CAFku-E2amDfNWh9jPSdQvR5XquWpHkw33zbb92K8X1di85s...@mail.gmail.com>
 <D445BA47-E08B-49CC-A135-EDC759C59...@typesafe.com>
From: James Moore <ja...@restphone.com>
Date: Thu, 20 Sep 2012 10:28:24 -0700
Message-ID: <CAPBr=W8GXftcQjaU-oGdeU9_VtWT_yXoSKq9b2s7bbAansY...@mail.gmail.com>
Subject: Re: [scala-ide-user] Improvement Request on Highlighting Implicit Conversions
To: scala-ide-user@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d040122e9c34f9b04ca2575a7

--f46d040122e9c34f9b04ca2575a7
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Sep 19, 2012 at 4:23 AM, Mirco Dotta <mirco.do...@typesafe.com>wrote:

> This discussion reminded me of a feature request I've been meaning to
> make for a while. Highlighting implicits and showing inferred
> semicolons is useful but perhaps already too cluttering, and I think
> Scala tooling would benefit from more desugaring info. I'd love to see
> a "Code Inspection" panel that mirrored a section of the currently
> focused source code (perhaps visually similar to the JDT's Declaration
> View) with toggles to show synthesized code such as  "implicits
> expansion", "inferred semicolons", "inferred member types",
> "for-comprehension desugaring", "extractor desugaring", etc.
>
>
That sounds great.  I'd also like it to be able to do the opposite:  take a
chunk of code, and remove everything that could be provided implicitly.
 Take out semicolons, parens, explicit types, etc, as long as the code
compiles to the same thing.  Sort of like a set of lenses for looking at
code - I think there's more than one view visible at a time, too.

I'd also like an option for named parameters (show / hide).

-- 
James Moore
ja...@restphone.com
http://blog.restphone.com/
http://www.linkedin.com/in/jamesmmooreiv

--f46d040122e9c34f9b04ca2575a7
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 19, 2012 at 4:23 AM, Mirco Dotta <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mirco.do...@typesafe.com" target=3D"_blank">mirco.dotta@typesafe=
.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

<div style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote type=
=3D"cite"><div>This discussion reminded me of a feature request I&#39;ve be=
en meaning to<br>make for a while. Highlighting implicits and showing infer=
red<br>

semicolons is useful but perhaps already too cluttering, and I think<br>Sca=
la tooling would benefit from more desugaring info. I&#39;d love to see<br>=
a &quot;Code Inspection&quot; panel that mirrored a section of the currentl=
y<br>

focused source code (perhaps visually similar to the JDT&#39;s Declaration<=
br>View) with toggles to show synthesized code such as =A0&quot;implicits<b=
r>expansion&quot;, &quot;inferred semicolons&quot;, &quot;inferred member t=
ypes&quot;,<br>

&quot;for-comprehension desugaring&quot;, &quot;extractor desugaring&quot;,=
 etc.<br></div></blockquote></div></div></div></blockquote><div><br></div><=
div>That sounds great. =A0I&#39;d also like it to be able to do the opposit=
e: =A0take a chunk of code, and remove everything that could be provided im=
plicitly. =A0Take out semicolons, parens, explicit types, etc, as long as t=
he code compiles to the same thing. =A0Sort of like a set of lenses for loo=
king at code - I think there&#39;s more than one view visible at a time, to=
o.</div>

<div><br></div><div>I&#39;d also like an option for named parameters (show =
/ hide).</div><div><br></div></div>-- <br>James Moore<br><a href=3D"mailto:=
ja...@restphone.com" target=3D"_blank">ja...@restphone.com</a><br><a href=
=3D"http://blog.restphone.com/" target=3D"_blank">http://blog.restphone.com=
/</a><br>

<a href=3D"http://www.linkedin.com/in/jamesmmooreiv" target=3D"_blank">http=
://www.linkedin.com/in/jamesmmooreiv</a><br>

--f46d040122e9c34f9b04ca2575a7--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
