Dru Jensen

@983 amazing investigative work on this. It's interesting to see how the compiler is optimizing the recursive calls. I am open to suggestions on how to improve the fairness of...

I think the best solution is to implement #85 and change the exmamples to take a parameter . This should prevent some of the optimizations made here but still allow...

I have moved back to allowing compiler optimizations. However, I will only allow compiler flags that are deemed safe and "release" quality i.e. -O3.

so I am wondering if @Blacksmoke16 can do his magic and support both the `assert` gem and then add macros to inject the annotation. This is how the mapping is...

I prefer something a little more rails like: ``` column email : String validate :email, format: email, presence: true, allow_blank: false ```

@damianham It looks like crystal is embracing annotations so not sure we have many options. The `inherited` or `finished` hooks cause other issues like you can't inherit from a Granite...

@Blacksmoke16 Just to clarify, I wasn't calling your `Assert` library a pig, I was calling the annotations syntax a pig. I think your code is absolutely beautiful and would love...

The way I envisioned people using Granite to handle aggregate queries is to build a new read only model for each query. Maybe this is too laborious of a solution....

what if we create new column types for each aggregate that takes a type ``? ``` class UserAgeByCountry < Granite::Base table :users column country : String, group_by: true column cnt_age...

Thanks @Blacksmoke16 and @sam0x17 for the feedback. I am torn if an ORM should return random query results or if that should be a separate product since its no longer...