What ' s the over under for the number of yards guide has in the second half ? <| sep |> This is a very good video of whatever it was but what pissed me off or rather irritates me is that if it were me driving , I would have turned the car to follow with the lights at least for a second or two more . They got up pretty close by the time it dissapeared off camera . <| sep |> Still shows up for me . Keep trying . Maybe there ' s just a lot of traffic . <| sep |> She looks awesome for 90 . Go grandma ! !<| sep |> I just ordered the SAAE trigger for my windham . I hope I figure out how to install it lol <| sep |> I think I ' d go with 2 beautiful women , one really strong and ugly man and one older and highly intelligent man . <| sep |> Hum . If I understand correctly There are all sort of pointer tables similar to vtable that are generated , but it ' s less obvious to the programmer what they will contain . The object still need to be dynamically allocated obviously but the allocation is completely hidden away , which isn ' t very cy to me . Inheritance is already a type of runtime ' concept ' in that it defines a set of requirements The fact that concepts are implicit is great at compile time but at runtime . not so sure . It ' s not because a class has a method foo that I meant for it to be used in a place that takes a virtual concept having that requirement . In other word , I don ' t think having a certain set of method signatures is enough to determine what is a valid user of a class . Given a virtual concept Foo , What is Foo ? Foo ? Foo . How many indirection are there between the instance of foo and the actual underlying object ? Is it on the stack on the heap , optimized away somehow ? How would the feature impact size binary , etc . My point is , I have the feeling it messes with the relatively simple memory model of C . Probably with a lot of edges cases and caveat that could hurt the readability and teachability . Do I miss something ?