Judah Jacobson

I think you'll need to add the new op to the blacklist: https://github.com/tensorflow/haskell/blob/739f6618f492a295ed9f8624076e0a6ddecdc683/tensorflow-core-ops/Setup.hs#L86 You're probably using a newer version of tensorflow than has been tested before with this library.

@skynet1 we mean the version of the Tensorflow C++ library itself that's installed on your machine, not these Haskell bindings. (For example, from https://www.tensorflow.org/install/lang_c).

You can import them from `TensorFlow.GenOps.Core` from the `tensorflow-core-ops` package; for example: https://tensorflow.github.io/haskell/haddock/tensorflow-core-ops-0.1.0.0/TensorFlow-GenOps-Core.html#v:round The full Haddocks are here: https://tensorflow.github.io/haskell/haddock So far the `TensorFlow.Ops` module only reexports a subset of `TensorFlow.Core.Ops`....

You can do something simpler: since you're just reexporting the functions without changing them, you can just list them in the export list directly as `CoreOps.round`, etc., without defining a...

That sounds like https://github.com/commercialhaskell/stackage/issues/2759 . I thought it was fixed in newer `stack` but am not certain off the top of my head. Maybe there's something that needs to be...

@awpr thanks for pinpointing the problem with the sdist file. I've created google/proto-lens#185 to use the `autogen-modules` field from Cabal-2.0, which lets us avoid including the generated files in the...

It looks like the kernel is more restrictive than the op (which allows int32 and int64): https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/kernels/reshape_op.cc#L54 https://github.com/tensorflow/tensorflow/blob/1a0742f6a7a06ff54481385b5c51094b0fef8cf3/tensorflow/core/ops/array_ops.cc#L1555 See discussion [here](https://github.com/tensorflow/tensorflow/issues/5886) which previously moved this error from runtime to graph...

@prednaz I disagree that "vertical space is not as precious as horizontal space" is universally true. Rather, I think it's a tradeoff. Just because you *can* scroll vertically doesn't mean...

Apologies, it was an oversight. I've merged haskeline-0.8 back into master. However, I'm not seeing d1c2cc6895dc2032ef54897e1fdab3d99f85629f in my history; which commit was that referring to?

This is supported as of 37535b9f5b8c96ea60fbc0ee2144f207fe56aa16, but currently ignores the version bounds. I'm not sure how many existing packages on Hackage require them for correct behavior.