RE: [GHC] #7685: :script command does not resolve ~
Should there be some documentation in the user manual?
(Apols if there already.)
Simon
| -Original Message-
| From: ghc-tickets [mailto:ghc-tickets-boun...@haskell.org] On Behalf Of
| GHC
| Sent: 09 October 2013 09:36
| Cc: ghc-tick...@haskell.org
| Subject: Re: [GHC] #7685: :script command does not resolve ~
|
| #7685: :script command does not resolve ~
| -+--
| --
| Reporter: nomeata |Owner:
| Type: bug | Status: patch
| Priority: normal|Milestone: 7.8.1
|Component: GHCi | Version: 7.6.2
| Resolution:| Keywords:
| Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
| Type of failure: None/Unknown | Difficulty: Unknown
|Test Case:| Blocked By:
| Blocking:| Related Tickets:
| -+--
| --
|
| Comment (by Joachim Breitner mail@…):
|
| In [changeset:ddc79b229d58c1bed8ae19b955b491436e015e96/ghc]:
| {{{
| #!CommitTicketReference repository=ghc
| revision=ddc79b229d58c1bed8ae19b955b491436e015e96
| GHCi: Expand ~ in :script command
|
| Fixes: #7685
| }}}
|
| --
| Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7685#comment:4
| GHC http://www.haskell.org/ghc/
| The Glasgow Haskell Compiler
| ___
| ghc-tickets mailing list
| ghc-tick...@haskell.org
| http://www.haskell.org/mailman/listinfo/ghc-tickets
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Turning ForceSpecConstr/NoSpecConstr into pragmas?
Hm, no, it's not exported anywhere currently. It could be exported from somewhere and marked with such a pragma, although then presumably we'd also need to persist that pragma to the interface file so client code sees it. This actually circles back to making some kind of library types to enforce this, e.g. making SPEC a builtin type specifically for this case (it would also remove the annoying gotcha that SPEC must be a sum-type where SPEC2 is unused, so the compiler doesn't outright eliminate it.) Although I don't know about the NoSpecConstr case - since that tends to be enforced on several different types in e.g. DPH. Presumably though, as the comments say - maybe we should just nuke NoSpecConstr, which would make that a non-issue. Then SPEC can be a special built-in type. On Wed, Oct 9, 2013 at 9:30 AM, Andrew Farmer afar...@ittc.ku.edu wrote: +1 for pragma, though the SPEC type is always the same anyway... is it exported from somewhere? It seems silly that I have to define and annotate my own version when I want to use it. I realize that doesn't solve your stage 1 problem... more of just a general question. -- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: ghc.haskell.org updated to Trac 1.0.1
Is there a way to get back the preview window as I'm writing a comment on a ticket? Perhaps I'm just missing the button somewhere, but I liked that window! Thanks! Richard On Oct 6, 2013, at 9:02 AM, Herbert Valerio Riedel h...@gnu.org wrote: Hello *, The Trac instances at ghc.haskell.org have been upgraded to the current stable Trac 1.0.1 release in order to alleviate some technical issues with the aging Trac 0.12.x line. Ideally, you shouldn't notice any regressions; however, as a side-effect Trac 1.0.x has a slightly different look which takes a bit getting used to. I've tried to tweak the navigation sidebar to match the new design and integrate better with Trac's variable-height notification div/s. Should you notice anything that has been broken by the upgrade, please let me know! For those interested in what's new in Trac 1.0, here's a subjective selection of Trac 1.0 highlights: - Improved the handling of ticket edit conflicts, by showing simultaneous edits and conflicting changes, and making it easier to merge the changes - Ticket comments can now be displayed threaded - Simplified reverting of a wiki page to an older version - Added a user preference and a option to display relative/absolute datetime - Added //Comments only// filter in the Ticket Change History preferences, to hide field changes from the history and even exclude entries without a comment For more details see http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#DetailedUserVisibleChanges Cheers, hvr ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: Turning ForceSpecConstr/NoSpecConstr into pragmas?
On Wed, Oct 9, 2013 at 7:13 AM, Austin Seipp aus...@well-typed.com wrote: Early last week I was reminded of something, which was that vector/dph depend on the stage2 compiler - this is because both packages use annotations to specify ForceSpecConstr and NoSpecConstr on several key datatypes. For most of our platforms (now including ARM,) this should generally be OK, because we have stage2 and the linker available to support it. But in particular, it makes vector and dph unusable for cross compilers. This might be somewhat problematic for e.g. iOS or an RPi, where we only have a stage1 cross compiler - but it's reasonable to assume we may want to use vector there! And more and more libraries depend on vector these days. I raised the same issue with Simon PJ a while ago. We ran into this problem when trying use GHC as a cross-compiler at Google. I think we should 1. Convert it to a pragma. 2. Look into a design that was suggested at ICFP, namely to put a pragma on the data type we want to get optimized away instead. -- Johan ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: GHC 7.8 Release Status Schedule
On Sat, Oct 5, 2013 at 9:25 AM, Austin Seipp aus...@well-typed.com wrote: - Nov 1st: Cut branch, and I plan on making a 7.8 RC1 available the same day, for several platforms. Hi, Austin - Thanks for writing this up. One of the factors that's blocking my ability to build Hackage packages is that Hackage does not contain versions of a number of bundled-with-GHC packages that have versions matching the versions shipping with HEAD. It would unblock that process somewhat if you were to upload new versions of unix and various other packages that are not yet in sync fairly soon, preferably well before cutting the branch. Thanks! ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
Re: GHC 7.8 Release Status Schedule
Indeed. There's a few straggling things but overall we're in feature freeze overall right now, right? On Wednesday, October 9, 2013, Johan Tibell wrote: On Wed, Oct 9, 2013 at 4:07 PM, Bryan O'Sullivan b...@serpentine.comjavascript:; wrote: One of the factors that's blocking my ability to build Hackage packages is that Hackage does not contain versions of a number of bundled-with-GHC packages that have versions matching the versions shipping with HEAD. It would unblock that process somewhat if you were to upload new versions of unix and various other packages that are not yet in sync fairly soon, preferably well before cutting the branch. Thanks! +1. Forgetting to upload GHC released packages altogether (even after the release) has been a problem in the past. I think we should aim for making releases of all the packages GHC ships with before we make the actual release. It will make sure 1) that's not forgotten and 2) people have more time to fix their packages. There's clearly a tension here: GHC might change last minute and break one of the just released packages again, forcing another release. If we release the packages once we enter feature freeze for GHC, that should be a rare occurrence. ___ ghc-devs mailing list ghc-devs@haskell.org javascript:; http://www.haskell.org/mailman/listinfo/ghc-devs ___ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
