labofsahil/github-event-dataset-2012 huggingface dataset:
`ev` => `event`
The format string has three format specifiers, but only two arguments.
any of the unit functions?
Das halte ich für gefährlich!
Stell dir vor, du machst reopen im Fall eines Reworks....
То есть посмотри, как в азотхе сделано.
Again, no point in calling `experimental`
:-1: 

I don't see the point to introduce inconsistencies by omitting the parenthesis only when there aren't parameters. Why exception ?

Including the fact that other OOP languages like Java, C++ & C# don't omit parenthesis (for calling constructor), it could be very confusing.

IMO, I think it's more readable when I take into account the magic __invoke() and dynamic class name.

$obj = new $className();
$obj = new $className;    // the same as above
$a = $obj();  // magic invoke
$a = $obj;    // copy

Just my 2 cents...
Can we use external CSS here?
Same here; this is just a local variable. I respect your opinion, Andrej, but please be aware that it's not necessarily the same as of other people contributing to druntime/Phobos (see e.g. Jonathan's reply on the NG).
Why the extra tab?
Yes, for this codebase the indentation should be consistently "2 spaces" (no tabs). And naturally lines that go on the next line should be intended, often heavily to align with parentheses etc. If these are not in README could you make sure they will be. Maybe there's some Ruby style guide that a link to it could also be added. Thanks!
Ugh yeah why can't this be easier! The other solution we could do is simplify the markdown view and not use the rails route helper explicitly. It's a little weird, but we could just use an instance variable: `@puzzle_url` which we set to `Rails.application.routes.url_helpers.puzzle_path(@puzzle)` in the controller. Better or worse? IDK. Either way seems kinda crappy to me. I'll have to think about this some more
`toggle`:n avulla:
~~~clojure
(defn parity [a-seq]
  (loop [s #{}
            [h & tail] a-seq]
    (let [s' (toggle s h)]
      (if (empty? tail)
        s'
        (recur s' tail))))) 
~~~
Too many dashes, should be `rwr---`
@kring I looked at this for a bit.  It's not obvious to me, but hopefully is to you.
This comment doesn't really apply anymore but overall I would say this is a good change. :cake:
Could you fix it (try to compile to be sure) and modify this PR?
I'm not actually sure. Since its meant to be run manually, its kind of useful to just kill it when you need, so its hard to know what timeout it should have.
Even if we make this strongly typed. this logic won't happen.
See #704 This is part of a larger potential bug (need more error-checking).
Try to use list of Roles
okh ajab eshtebahe faheshi!!
ehtemalan eshtebahi Enter zadam!!
mano bebakhshid gholmidam dg azin jesarata nakonam! :))))
This should be `0.0400`.
why are you getting another reference to the questionnaire object - you already have one called quest (that you created on line 25 - although your method of getting the questionnaire is better, as you are using the get_object_or_404, maybe refactor to use this line on line 25, and then use the this_questionnaire reference throughout.
is there any reason we've kept it as tic tac toe other than tradition?
Django doesn't provide user registration. This feature A) provides the basis for the requirements of the other two features, B) shows us the developers knowledge of model forms and basic views in general, since the game will be JSON, and won't give us much insight into their basic CRUD-ish patterns (e.g., do they naturally use CBV without being told to, do they make base views, decorate `dispatch`, etc.). It's nice to know how a developer handles basic problems.
missing public here
this should not be changed
Erm...yes, indeed ;-) Thanks. Will include it in a fixup commit after we've been through comments...
Детектор поля "Тема" уже не нужон. Хотя, мало ли, на будуюсчее.
addressed with Jeff on the phone
This seems like a workaround instead of a fix. If the original code works on Android, this is a platform issue.
no, there is a difference between var and dynamic (since C# 4.0 both are present, var is there already since C# 3.0)

var - is known at compile tme and is not dynamic, once the type has been defined (at the first assignment, it's fixed and cannot be changed
the compiler even checks if you try to define different types to var and throws an error

dynamic - is what Visual Basic is supporting without Option Explicit and only known at run time

to see the difference maybe even clearer and easier - for var you have itellisence in Visual Studio - which wouldn't be possible if the type isn't known by the compiler. for dynamic it's missing.

I agree, that also var shjouldn't be used too often, and mostly not for variables which are used over a longer period in a method, but i just want to clarify that i'd never use a dynamic typed variable in C# (except when using COM interop, but this kills you without dynamic)
Exercise asked for only a one comparison with three parameters. No points from this one.