11:59 <FromGitter> <foi> Hi! How to use HTTP::Server as multithread (not multiprocess!)

11:59 <FromGitter> <foi> ```code paste, see link``` ⏎ ⏎ This is single threaded [https://gitter.im/crystal-lang/crystal?at=5b66e6ace9ab53770c918ead]

11:59 <Groogy> Think there is a Thread class but not sure how well Crystal support it at this point

11:59 <FromGitter> <Qwerp-Derp> To implement threads for Windows, is it basically just porting the same code in the existing POSIX implementation, but changing things a bit so that they work properly for Windows instead?

12:00 <FromGitter> <Qwerp-Derp> There is a `Thread` class but it's used internally, you just use `Fiber`s and `#spawn` and instead

12:00 <FromGitter> <foi> if i wrap context in spawn do end - http server returns nothing

12:01 <Groogy> @Qwerp-Derp Fibers are not multi-threaded though?

12:01 <Groogy> Unless that changed recently they just let you switch context within same thread for long operations like IO etc.

12:06 <FromGitter> <Qwerp-Derp> oh didn't know that

12:06 <Groogy> From what I remember fibers only let another fiber do work if you yield

14:17 <FromGitter> <S-YOU> How many number of arguments in this function(clear_screen) of struct member? ⏎ ⏎ ```struct TextOutput ⏎ clear_screen : (TextOutputProtocol * -> Uint64T) ⏎ end``` [https://gitter.im/crystal-lang/crystal?at=5b6706e7c79ebc1ae7af36aa]

14:19 <FromGitter> <S-YOU> Compiler expects 0

15:01 <FromGitter> <foi> Sorry. It is my fault. HTTP::Server is multithreaded (or evented) by default. I've test from 1 browser and multiple tabs and it behaves as single threaded, but if use another browsers (or clients) it is not blocks and works as expected.

18:12 <FromGitter> <fridgerator> @foi You have to use `reuse_port` and run multiple servers that bind to the same port

18:12 <FromGitter> <fridgerator> https://crystal-lang.org/api/0.25.1/HTTP/Server.html#listen%28port%3AInt32%2Creuse_port%3ABool%3Dfalse%29-instance-method

18:18 <oprypin> so much misleading info :(

18:18 <oprypin> foi, you can't use multiple threads. but it's fine, the default behavior is still concurrent, using fibers. for multiple processes, see ^

19:38 <Groogy> Ugh I'm missing my sorted insert pull request right now :(

19:44 <Yxhuvud> What would you use it for this time?

21:11 <Groogy> priority queue

21:12 <Groogy> for my A* and Dijkstras algorithm

21:12 <Groogy> It's weird we don't want it in our standard library when most others do

21:13 <Groogy> and from what I could tell there's not really a good interface to find out where to put an element besides bsearch_index in Crystal

21:14 <Groogy> would say it's a place where we are severly lacking at