Reputation
1,298
Top tag
Next privilege 2,000 Rep.
Edit questions and answers
Badges
4 16
Impact
~10k people reached

Jul
24
accepted Union on Associations (Kernel Kill)
Jul
23
awarded  Nice Question
Jul
23
comment Why did Wolfram Research change their release policy?
@AndreasLauschke Yes but my point is that with finite resources "cutting corners on testing" might also result in earlier access to new functionality . From my own perspective (and it is my own so I don't want to make too broad a claim about "should") I would still have preferred a 2014 V10 release with all the new Data Science possibilities (functional but yes with some bugs and curious design decisions that have been annoying but not fatal) as opposed to a more watertight late-2015 release.
Jul
23
comment Why did Wolfram Research change their release policy?
My sense is that recent, more frequent versions are more buggy but the flip side is access to functionality sooner. Whether you think this is a good or bad idea depends on the extent to which this affects your set-up. My recollection from WTC 2014 was that the rationale was an improved, "streamlined technology stack" allowed this new release schedule although I don't recall anything explicit about weighing a new trade-off between correctness and earlier-access.
Jul
22
accepted A pre-parsed HoldForm
Jul
22
comment A pre-parsed HoldForm
Good stuff. See answer for use-case. A full pre-parsed HoldForm is nearly there MakeExpression[R : RowBox@{"HoldForm", "[", _, "]"} | RowBox@{"HoldForm", "@", _} | RowBox@{_, "//", "HoldForm"}, StandardForm] := HoldComplete@RawBoxes@R returns the HoldForm output but in raw boxes. A final ToExpression@First@ then completes the process but to do so in one hit, I suspect a MakeBoxes on each function form [],@,// is needed.
Jul
22
revised A pre-parsed HoldForm
provide use-case answer
Jul
21
comment A pre-parsed HoldForm
Great. Looks workable. I will have a look at it tonight. B.T.W note that "RawBoxes" instead of "DisplayForm" seems to mean that "LoseRespect" is not necessary?
Jul
21
comment A pre-parsed HoldForm
... that with things not generated on the fly users receive a frozen-version's output [not an unimportant consideration given how fluid the Data Science functionality seems these days]). Unfortunately even this doesn't work with $PreRead in a package set-up since while the "input form" is preserved in a .m file when assoc = <|f@x -> (x // g)|> is placed in an initialization cell, reading this back in bypasses $PreRead's setting (a condition I didn't mention in the question).
Jul
21
comment A pre-parsed HoldForm
Yes, you might be right. I do get nervous though about tinkering with $PreRead (even if your succinct solution does seem watertight). In particular, I kind of wanted to avoid its use as it seems like bad form to potentially distribute a notebook with $PreRead altered (since things are no longer isolated as with packages). Your solution could still be useful though in the use-case of just demonstrating user-input since this could be pre-generated prior to distribution (i.e. $PreRead changed during generation but not required from the users end - with the possible drawback ...
Jul
20
accepted Temporarily setting built-in function options at lower levels
Jul
20
comment Temporarily setting built-in function options at lower levels
Thanks, yes the Style solution serves my immediate purposes. It does highlight however, that I was using a sledgehammer to crack a nut as the broader utility of TemporarilySet is not tapped into (e.g. using in-built option settings and/or doing so "per function"). As noted, there were some issues with this broader application but will cross that bridge when next seeing it.
Jul
20
comment A pre-parsed HoldForm
Because this relates to parsing, the use of PreRead, RawBoxes etc seems unavoidable although in this use case this seems disproportionate, unjustified spelunking. Functions like Inactivate/Activate perhaps suggest new attention to formatting of Input forms which made me wonder if a PermanentRespect is implementable at a higher level.
Jul
20
comment A pre-parsed HoldForm
PermanentRespect should also not have lingering side affects. e.g. FleetingRespect pollutes the name space while ensuring that Association formats with <| |> has unexpected consequences (e.g. AssociationMap[f]@<|a->1|> goes into infinite recursion )
Jul
20
asked A pre-parsed HoldForm
Jul
19
revised Association's Key[key] extraction different in V10.1/V10.2
added 4 characters in body
Jul
19
revised Association's Key[key] extraction different in V10.1/V10.2
edited title
Jul
19
revised Association's Key[key] extraction different in V10.1/V10.2
edited title
Jul
19
revised Association's Key[key] extraction different in V10.1/V10.2
added 11 characters in body
Jul
19
revised Association's Key[key] extraction different in V10.1/V10.2
deleted 1 character in body