search

haxetink / tink_chunk

Chunks of readonly binary data.
The Unlicense
8 stars 5 forks source link

Typing issue #14

Closed Lazarus404 closed 3 years ago

Lazarus404 commented 4 years ago

When compiling tink_http for Java, I get:

haxelib/tink_chunk/0,3,0/src/tink/chunk/ByteChunk.hx:72: characters 4-14 : tink.chunk.ByteChunk should be tink.Chunk
back2dos commented 4 years ago

As it is 3.0.1 passes the CI with java on both Haxe 3.4.7 and 4.0.0, so the issue must be specific to your build configuration. Please provide any details that could help in reproducing this ;)

Lazarus404 commented 4 years ago

So, I also get this with the CS target. If you use the Fetch example from tink_http, you should see this issue. I'm using Haxe 4.0.2

robGetsTheJobDone commented 4 years ago

Any updates on this issue @Lazarus404 I am running into a similar issue.

cedx commented 3 years ago

Haxe 4.1.4 (Windows x64) : same issue here with tink_http 0.9.1 when targeting the JVM (tested with hxjava 3.2.0 and 4.0.0-alpha). The target URL is a https one: the underlying client is SecureSocketClient.

return Client.fetch(url).noise();
// tink_chunk/0,3,1/src/tink/chunk/ByteChunk.hx:72: characters 5-15 : tink.chunk.ByteChunk should be tink.Chunk
kevinresol commented 3 years ago

I guess this is fixed by https://github.com/haxetink/tink_chunk/commit/ac3430b9720765d2d842d82652a238ed20c2b52d?w=1

cedx commented 3 years ago

Indeed, if I use the Git version of tink_chunk, the problem is fixed. So we just have to wait for the release of a new version on Haxelib. Thanks @kevinresol.