the fact that .net framework like 4.5 is still damn around is incredible
the fact that .net framework like 4.5 is still damn around is incredible
KShould release Silk 1.123 and say it's LTS
Kjust take whatever comes out of trying to build Silk 1.x and see what happens
Kturns out like half of windows relies on framework 4.5 lmao so theyre stuck keeping it around
PSilk 1.x will still build
PQuickly, too
Kyeah if it comes preinstalled on windows I will believe it
Pregenerating will still work as well
K
ready for LTSPHAHAHAHAHAHAHAHAHAHA
Poh I didn’t mean to do caps but that added to the effect
KI did imagine a brit with a cowboy hat spitting out some tea
Kso good job xD
PI identify as all the stereotypes 
KI know xD
Kthing with british people seems to be that the stereotypes are just all true
Pyeah the worlds pretty spot on there
K@Perksey you also started your degree now no? Not sure what your setup is like now?
PNot yet
PDon’t ask, quite salty
PTLDR I HATE THE IRS
Pwill be starting in April maybe
Kwell shit
Kalso I can agree I hate the (german equivalent of) the IRS
KGot my funds frozen few weeks back 
PHMRC is pretty good in my experience
Pwell the UK gov seems pretty good in general when put in perspective with the U.S.
Pthe U.S. still has LOADS of paper forms
Pwhereas the UK has barely any left
PI’ve had to fill in one in my entire lifetime I think
KSeems like the UK just has a fairly decent system to streamline processes + digitalization
Khere digital files are still considered not legally binding so Fax is the most digital you'll get
Kpfffffff germans love their burocracy so that will never happen here
Ktbf US authorities seem to just kind have fucked themselves. .... SSN is a good system
PSSN is not a good system
Pstill lots of very absurd paper forms
PSSA offices needed everywhere
Pthey have nothing on UK’s NINO
KI only had to deal with the like tax exemption related papers so far and have just winged it - never heard anything from it and I'm not planning to ask them about it again
Pah the W-8BEN
PI’m stuck on the W-7 which literally won’t let me apply for an ITIN (basically an SSN stand-in for tax purposes) until April because of all the silly rules
C@Perksey Where is a good place to handle the initial Pointer class generation?
also do we have a place where we will make decisions on when we use these types, and would need to add additional higher dimension types?
also do we have a place where we will make decisions on when we use these types, and would need to add additional higher dimension types?
PI’ve just been shoving rarely-used code and scripts somewhere in the
Not sure what you mean for the second question. The proposal process basically involves us making a decision and documenting it in the proposal (optionally including alternatives), and then debating and/or justifying decision to the working group in a meeting. Often this involves a few proposal revisions before it gets approved.
engNot sure what you mean for the second question. The proposal process basically involves us making a decision and documenting it in the proposal (optionally including alternatives), and then debating and/or justifying decision to the working group in a meeting. Often this involves a few proposal revisions before it gets approved.
Pas for the usage and dimensions, these need to be documented in the proposal I think - I don’t remember writing any words around it yet.
The code that generates code that uses it is in SilkTouchX
The code that generates code that uses it is in SilkTouchX
CI meant more in code, the proposal discusses higher dimensions than 3 being built as needed on the fly as needed. I was thinking about whether it was feasible to add those in now as well, whether as as a mod or part of some generation step.
If we still aren't sure I can just get the generator stood up and we can decide on how it is used later.
If we still aren't sure I can just get the generator stood up and we can decide on how it is used later.
PI think 3 is the highest dimension I’ve ever seen in a silk binding, so 3 makes sense until we spot a use case (in the form of a generator crash :P) that warrants increasing it
Pwhich is why I’m keen on keeping the generation code you’re writing around in hopes that if that day comes it’s just a case of increasing a number somewhere
CThe way it is setup currently, I was just going to back it with a binary tree to track what exists and then we request a type to be generated it either generates it on the spot or when we are finished we generate all the types in the tree. This would keep to only the types we need and expand without crashing. Since the types are reliant on the outer type being available (aka PtrMutPtr requires MutPtr) this method should work fairly well and require little upkeep.
I would just populate it with the base 3 levels ahead of time to catch the general cases.
I would just populate it with the base 3 levels ahead of time to catch the general cases.
Pit’s a smart idea, and one we could implement if ever we want to add a “coreless” mode to SilkTouchX.
Pi mean we could do that if you wanted to add that to SilkTouchX. i'm keen to have dimensions up to three present in Silk.NET.Core, and also keen to make sure that for Silk.NET first-party we crash if a binding needs more than 4 (so we can add these to Silk.NET.Core instead of potentially multiple assemblies having duplicate higher-dimension pointers), but for third-party users that may not want to use Silk.NET.Core it certainly makes sense
Pi have no idea how all of those constraints would look when added to the generator though, probably some code-sharing between
UseSilkDSL