Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:44
    mamantoha closed #12567
  • 14:37
    beta-ziliani edited #12568
  • 14:35
    beta-ziliani opened #12568
  • 13:23
    Blacksmoke16 labeled #12567
  • 13:18
    Blacksmoke16 labeled #12567
  • 13:06
    mamantoha synchronize #12567
  • 13:05
    mamantoha edited #12567
  • 13:03
    mamantoha synchronize #12567
  • 12:12
    mamantoha synchronize #12567
  • 12:10
    mamantoha opened #12567
  • 11:23
    straight-shoota synchronize #12541
  • 11:15
    straight-shoota closed #12530
  • 11:14
    straight-shoota closed #12564
  • 11:14
    straight-shoota demilestoned #12564
  • 11:14
    straight-shoota milestoned #12564
  • 11:14
    straight-shoota demilestoned #12564
  • 11:14
    straight-shoota milestoned #12564
  • 10:45
    straight-shoota milestoned #12564
  • 10:45
    straight-shoota milestoned #12564
  • 10:45
    straight-shoota labeled #12564
moe
@moe:busyloop.net
[m]

ha, yea, you're pointing right at the hard part.
at first i had the models generate their swagger-schema.

but then i realized, endpoints often only return a partial view of a model
(i.e. you don't want to include the password-field with users and don't want
that mentioned in the swagger-docs either).

so... it's kinda annoying, i guess my renderers (aka serializers)
have to be aware both of their model and the endpoint.

maybe it's just not solvable without really forcing the user
to explicitly declare it...

George Dietrich
@Blacksmoke16
prob a good idea to have a separate object used to represent payload/responses versus assuming that is going to match the DB model 1:1
crystal stdlib and some shards have the ability to like exclude serializing the password on serialize but accept it on deserialize, but DTO would be a more robust way to go about that imo
esp for more complex models so that the structure of the request doesnt need to be tightly coupled to the db schema
moe
@moe:busyloop.net
[m]
yea, rails has ActiveModelSerializer for this. guess i may just want too much ("just return whatever you want, we'll render & auto-doc it").
works fine up to the point of auto-doc'ing & validating the input parameters. but the return value, that's really a tough cookie.
George Dietrich
@Blacksmoke16
ultimately you'd need to define what those validations are somewhere
using a DTO for that would get you that + the structure of the request
and have another for the response that describes the response
moe
@moe:busyloop.net
[m]
yup. i'll dig more into it in the coming days.
George Dietrich
@Blacksmoke16
could use the validation component for that ;)
but sounds good :+1:
Hayden Jones
@wrq
does crystal having anything like timeit for python? I've never profiled before, but I'm trying to determine where to use Structs and where to use tuples and such in a large data model, and I was hoping to put together numbers for the performance of each design
George Dietrich
@Blacksmoke16
structs and tuples are both on the stack so they'd be essentially the same. Is suggested to use structs over tuples/namedtuples majority of the time anyway
Hayden Jones
@wrq
okay, that makes sense
thank you
George Dietrich
@Blacksmoke16
but to answer your question, i'd checkout https://crystal-lang.org/api/master/Benchmark.html
Hayden Jones
@wrq
AH, okay. I'm embarrassed that I missed that, what an obvious name for it
jwaldrip
@jwaldrip:matrix.org
[m]
Is 1.4 dropping today?
I saw the release nodes reference todays date
George Dietrich
@Blacksmoke16
sure looks like it, or if not very soon
jwaldrip
@jwaldrip:matrix.org
[m]
Does the new version still require a compile time flag to get the interpreter?
Or is it enabled by default now?
George Dietrich
@Blacksmoke16
still need to manually build it with the flag
Hayden Jones
@wrq

I want to implement something like a dispatch table for a series of pseudo-bytecode instructions. I'd like to lookup each instruction and then yield my little VM to a proc, and execute each instruction that way.

Is this wise? And also, I don't see a yield_self method, am I missing something crucial?

Hayden Jones
@wrq
oh, that's wonderful. thanks again. I swear I actually can read, I guess I just overlook all the good stuff!
George Dietrich
@Blacksmoke16
iirc there are some issues with tho
so debatable if its worth just not declaring a block arg
but if it works fine for your use case :+1:
Hayden Jones
@wrq
Do you think it makes more sense then to just implement all the bytecodes as methods under the main VM class? I had already thought of that, but it just seemed inelegant. I haven't worked with a statically typed language before, so I don't really have the right intuition for this sort of thing. If it were ruby, I would just have the VM object be very simple and then have a big hash of procs as the values and use yield_self to execute them by passing in the vm object
George Dietrich
@Blacksmoke16
Got some example code?
doesn't compile, just a quick example I crapped out
I'm writing my own Push interpreter
but that's the general idea for execution
From IRC (bridge bot)
@FromIRC
<riza> @wrq it seems like a good use of a macro to generate a dispatch method based off of some classes or methods
<riza> i suppose it depends on how many instructions are in your instruction set
Hayden Jones
@wrq
I've been dreading learning macros, but that's because I'm lazy
George Dietrich
@Blacksmoke16
any reason to not just have them as methods on vm versus passing that in?
would have to benchmark what would be more performant, but i imagine having methods on the same type would be than a bunch of procs
Hayden Jones
@wrq
I have no clue, but I trust your intuition and I suppose I'll just do it that way
From IRC (bridge bot)
@FromIRC
<riza> the benefit to macros is you can generate code which is very performant but still maintainable, paying the conversion cost at compile time rather than at runtime
<riza> going along with what Blacksmoke has suggested, you could easily make a macro that collects all the methods on your VM class, filters out methods with a prefix, and generates the parser/dispatcher for that
<riza> So adding an instruction to your bytecode is as simple as defining a method called instruction_add
Hayden Jones
@wrq
right, I definitely want to do as much as possible before runtime. Alright, well this has been very helpful information. I suppose I'll spend some time with macros and do it with methods.
Ary Borenszweig
@asterite
Always start without macros. Add macros if you find repetition in your code
Hayden Jones
@wrq
I gotta get used to that. I am not a huge fan of metaprogramming in Ruby, I've always envied the FP style of things. I know that macros aren't exactly the same and offer much stronger guarantees. I'm reading up now on macros in crystal.