Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Cary Robbins
    @carymrobbins
    for new systems
    Reggie Perry
    @reggieperry
    Question: Does haskforce support typed holes?
    Cary Robbins
    @carymrobbins
    (assuming that's the issue)
    Barry Burd
    @allmycode_twitter
    I still keep getting that AesonException "Error in $.packages.cassava.constraints.flags: on the command line on the Mac.
    Cary Robbins
    @carymrobbins
    @allmycode_twitter oh that seeems like some issue with stack
    Barry Burd
    @allmycode_twitter
    I'll try reinstalling stack on the Mac
    Cary Robbins
    @carymrobbins
    @allmycode_twitter this issue sounds familiar...may be worth a google
    @reggieperry nothing stops you from using type holes, although i recently added parser support for them so they won't appear red in the IDE. that will be released soon.
    Reggie Perry
    @reggieperry
    The reason I ask is because typed holes with the new valid-hole-fits feature would be very powerful in IntelliJ to aid in type driven development. I would be curious as to how tough that would be to implement in haskforce.
    Cary Robbins
    @carymrobbins
    @reggieperry haskforce currently has ghc-mod integration, and i believe ghc-mod provides something like this (the refine command)
    i'm not sure if this completely handles your use case, feel free to open a feature request on the haskforce issue tracker. i'll be able to add details there about what may be needed for implementing this
    Cary Robbins
    @carymrobbins
    oh and -frefinement-level-hole-fits looks interesting as well
    Barry Burd
    @allmycode_twitter
    @carymrobbins You said "the Haskell Stack Run is for running your compiled binary, not for running ghc" so I get "Executable named ... not found on path". I don't see any executable that's been created in any of the project directories.
    Cary Robbins
    @carymrobbins
    @allmycode_twitter Right, so first your build must succeed. Your binary name is defined in your cabal file (or package.yaml). The analogous workflow on the command line would be -
    $ stack build
    $ stack exec <compiled-executable-name-from-cabal-file>
    if stack build fails, you can't exec the binary because it doesn't exist yet
    Barry Burd
    @allmycode_twitter
    I thought I already had a successful build after importing a project that I created on the command line, but I'll keep poking around.
    Cary Robbins
    @carymrobbins
    to debug this, what is the result of stack build from the command line?
    Barry Burd
    @allmycode_twitter
    stack build
    [1 of 2] Compiling Main ( /Users/barryburd/.stack/setup-exe-src/setup-mPHDZzAJ.hs, /Users/barryburd/.stack/setup-exe-src/setup-mPHDZzAJ.o )
    [2 of 2] Compiling StackSetupShim ( /Users/barryburd/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /Users/barryburd/.stack/setup-exe-src/setup-shim-mPHDZzAJ.o )
    Linking /Users/barryburd/.stack/setup-exe-cache/x86_64-osx/tmp-Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 ...
    clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
    clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
    Building all executables for `HaskForceCreatedWithStackCommand' once. After a successful build of all of them, only specified executables will be rebuilt.
    HaskForceCreatedWithStackCommand-0.1.0.0: configure (lib + exe)
    Configuring HaskForceCreatedWithStackCommand-0.1.0.0...
    clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
    HaskForceCreatedWithStackCommand-0.1.0.0: build (lib + exe)
    Preprocessing library for HaskForceCreatedWithStackCommand-0.1.0.0..
    Building library for HaskForceCreatedWithStackCommand-0.1.0.0..
    [1 of 2] Compiling Lib ( src/Lib.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Lib.o )
    [2 of 2] Compiling Paths_HaskForceCreatedWithStackCommand ( .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/autogen/Paths_HaskForceCreatedWithStackCommand.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/Paths_HaskForceCreatedWithStackCommand.o )
    Preprocessing executable 'HaskForceCreatedWithStackCommand-exe' for HaskForceCreatedWithStackCommand-0.1.0.0..
    Building executable 'HaskForceCreatedWithStackCommand-exe' for HaskForceCreatedWithStackCommand-0.1.0.0..
    [1 of 2] Compiling Main ( app/Main.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/HaskForceCreatedWithStackCommand-exe/HaskForceCreatedWithStackCommand-exe-tmp/Main.o )
    [2 of 2] Compiling Paths_HaskForceCreatedWithStackCommand ( .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/HaskForceCreatedWithStackCommand-exe/autogen/Paths_HaskForceCreatedWithStackCommand.hs, .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/HaskForceCreatedWithStackCommand-exe/HaskForceCreatedWithStackCommand-exe-tmp/Paths_HaskForceCreatedWithStackCommand.o )
    Linking .stack-work/dist/x86_64-osx/Cabal-2.2.0.1/build/HaskForceCreatedWithStackCommand-exe/HaskForceCreatedWithStackCommand-exe ...
    clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
    clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
    HaskForceCreatedWithStackCommand-0.1.0.0: copy/register
    Installing library in /Users/barryburd/IdeaProjects/HaskForceCreatedWithStackCommand/.stack-work/install/x86_64-osx/lts-12.24/8.4.4/lib/x86_64-osx-ghc-8.4.4/HaskForceCreatedWithStackCommand-0.1.0.0-FSht0SwUqhaBKIg0yZqz6G
    Installing executable HaskForceCreatedWithStackCommand-exe in /Users/barryburd/IdeaProjects/HaskForceCreatedWithStackCommand/.stack-work/install/x86_64-osx/lts-12.24/8.4.4/bin
    Registering library for HaskForceCreatedWithStackCommand-0.1.0.0..
    new-host-10:HaskForceCreatedWithStackCommand barryburd$
    Cary Robbins
    @carymrobbins
    btw you can wrap the output in triple backticks to make it easier to read
    like this
    that said
    Installing executable HaskForceCreatedWithStackCommand-exe in ...
    so you want to run
    stack exec HaskForceCreatedWithStackCommand-exe
    Barry Burd
    @allmycode_twitter
    OK. Got to go now but I'll try it (and I'll use backticks in the future where necessary). Thanks.
    Cary Robbins
    @carymrobbins
    sounds good. last thing - in haskforce the executable name is HaskForceCreatedWithStackCommand-exe
    the name is defined in your cabal file
    Reggie Perry
    @reggieperry
    @carymrobbins Will do. Thanks.
    Andrei Dziahel
    @develop7
    hey @carymrobbins, are there any plans on adopting Eta for plugin development?
    Rahul Muttineni
    @rahulmutt
    @develop7 @carymrobbins was working on the Eta Intellij plugin which is written (in as much as Eta’s interop features allow) in Eta itself. A lot of it took inspiration from haskforce code, so when Eta can compile GHC & support more interop features, haskforce should be able to use Eta completely w/o depending on other languages.
    Andrei Dziahel
    @develop7
    @rahulmutt got it, thanks!
    Cary Robbins
    @carymrobbins
    @rahulmutt @develop7 The most recent stuff i think is in the eta-ide branch. There's also some Psi parser combinators for building intellij parsers which is pretty nice.
    Andrei Dziahel
    @develop7
    @carymrobbins @rahulmutt I've skimmed through source and there are a lot of reimports of IDEA SDK.
    Rahul Muttineni
    @rahulmutt
    @develop7 Yes, that’s the FFI boilerplate for binding against the required SDK APIs - we’re currently working on removing the boilerplate with some new features in Eta itself. There should be some modules that actually do something.
    Cary Robbins
    @carymrobbins