DDraceNetwork - developer

DDraceNetwork

Development / developer

Development discussion. Logged to https://ddnet.org/irclogs/ Connected with DDNet's IRC channel, Matrix room and GitHub repositories — IRC: #ddnet on Quakenet | Matrix: #ddnet-developer:matrix.org GitHub: https://github.com/ddnet

Between 2023-12-19 00:00:00Z and 2023-12-20 00:00:00Z

lerato

5 am, im finally done with 1st site in my life

03:37

hope last

03:37

rate pls

03:37

https://stormaxs.github.io/StA-site/

StA client is an exendeded Teeworlds|DDNet Client

wait what

04:33

LERP tee animation?

04:33

what does that mea

04:35

also @-StormAh~ is it alright that i give out thoughts about this client?

Voxel

LERP tee animation?

Linear interpolation

Voxel

also @-StormAh~ is it alright that i give out thoughts about this client?

Ofc, go for it

on 2560x1440 the buttons arent centered LOL

Image attachment

I fixed it already

04:37

Someone reported me when i released it last time

04:38

Cause im planning to done with stat page and only then make a new release

[ddnet-maps:master] 1 new commit

23fb026 M Nordrhein-Westfalen, M Borace, M GetSpeed, M run_as_a_pro - ddnet-maps

Voxel

on 2560x1440 the buttons arent centered LOL

The logo is missing an "r"

STA CLIENTR

troll

Trollr

Jupstar ✪

The logo is missing an "r"

Star client? poggers2

poggers2

-StormAh~

Star client? poggers2

poggers2

08:10

Also add ✪

I can't

08:11

I haven't sleep almost 2 night

08:11

Let me

08:11

Sleep

pepeLost

Ok, you can sleep for 10 minutes

Deadge

08:12

blushWokege

how dare he

08:14

stop sleeping - go work

alr alr

08:15

1 buf fix

Rust needs a 'inline lifetime, that makes sure a reference is only valid for a single expression. Would be cool and useful

Jupstar ✪

Rust needs a 'inline lifetime, that makes sure a reference is only valid for a single expression. Would be cool and useful

i mean cant u do that with a block {}

09:16

let b = 2;
{
  let b = &b;
}

09:16

use shadowing to achieve it

09:16

idk

Ryozuki

i mean cant u do that with a block {}

I mean e.g. if i return a mut ref from function call

09:16

That you can't truly borrow this result

@Jupstar ✪ there is something called fnonce

09:16

https://doc.rust-lang.org/std/ops/trait.FnOnce.html

FnOnce in std::ops - Rust

The version of the call operator that takes a by-value receiver.

09:16

Instances of FnOnce can be called, but might not be callable multiple times. Because of this, if the only thing known about a type is that it implements FnOnce, it can only be called once.

09:17

idk how u could achieve that u want xd

09:17

but if u can only use the ref inside a fnonce

09:17

maybe its possible

Well what i actually want is to return a Ref<'inline, T> Xd

xd

09:18

OnceCell?

09:18

ah no this is to write

09:18

idk

Yeah dunno. 2024 edition clearly needs a new rfc

well u should explain ur use case in depth

Yeah i want to return a borrow_mut. But this is unsafe, in logic sense, in combination with rc because you could end up borrow twice. But if the borrow would end every line+ i have a strict hierarchy of my types => safe af

09:21

Rn i am emulating with by not allowing public types and rewrite the public interface with a proc macro

09:22

Works well, but more hidden logic xdd

09:23

With some inline lifetime i could use deref trait (the inline lifetime also needs other requirements, but too much to list them, e.g. no inline lifetimes twice, or specific evaluation order of calls etc. xd) (edited)

09:23

Would be clean af

deref should only be used by smart pointers btw

09:25

Implementing Deref for smart pointers makes accessing the data behind them convenient, which is why they implement Deref. On the other hand, the rules regarding Deref and DerefMut were designed specifically to accommodate smart pointers. Because of this, Deref should only be implemented for smart pointers to avoid confusion. For similar reasons, this trait should never fail. Failure during dereferencing can be extremely confusing when Deref is invoked implicitly. Violating these requirements is a logic error. The behavior resulting from a logic error is not specified, but users of the trait must ensure that such logic errors do not result in undefined behavior. This means that unsafe code must not rely on the correctness of this method.

Well mine would be smart wrapper

Ryozuki

Implementing Deref for smart pointers makes accessing the data behind them convenient, which is why they implement Deref. On the other hand, the rules regarding Deref and DerefMut were designed specifically to accommodate smart pointers. Because of this, Deref should only be implemented for smart pointers to avoid confusion. For similar reasons, this trait should never fail. Failure during dereferencing can be extremely confusing when Deref is invoked implicitly. Violating these requirements is a logic error. The behavior resulting from a logic error is not specified, but users of the trait must ensure that such logic errors do not result in undefined behavior. This means that unsafe code must not rely on the correctness of this method.

the doc was recently updated btw: https://github.com/rust-lang/rust/commit/58645e06d9121ae37654b812d14041d0229d49c3

Rollup merge of #110340 - jmaargh:jmaargh/deref-docs, r=Mark-Simula...

Deref docs: expand and remove "smart pointer" qualifier Ready for review ~~This is an unpolished draft to be sanity-checked~~ Fixes #91004 ~~Comments on substance and cont...

09:39

so no smart-pointer it must be fail safe, the wrapper type should not have API collisions

09:39

also should not != must not

Jupstar ✪

Yeah i want to return a borrow_mut. But this is unsafe, in logic sense, in combination with rc because you could end up borrow twice. But if the borrow would end every line+ i have a strict hierarchy of my types => safe af

Can't you take the mut borrow out of the rc?

Learath2

Can't you take the mut borrow out of the rc?

what do you mean?

09:44

the whole Rc<RefCell>> would be wrapped in a smart wrapper

09:45

so u can never acess the refcell interface directly

Yes that's sort of what I meant

i mean i didnt 100% think through the best solution, but i think it would have potential xdd (edited)

Or whatever function is returning the mut borrow would take the rc in exchange

Learath2

Or whatever function is returning the mut borrow would take the rc in exchange

but i can clone Rcs

But the refcell wont allow a second mut borrow and enforce it at runtime

yes that's exactly what i dislike xD

09:48

at runtime xD

Ah you want to avoid the refcell?

i want to avoid lifetime (rc) but also the problem of calling borrow_mut twice (refcell)

09:49

i have a solution for this, it's just not nicest to use, bcs it requires adding proc macros to many types.. so it's also not enforced in that sense anyway

09:50

the 'inline would also not enforce it, but it would make my solution more elegant xD

09:51

e.g. if you never have cycling refs (not even with Weak) ,also not by passing Rcs around, you should™️ never have problems and still have the benefits of Rc

09:52

oh and hierarchically it is not allowed to have the same Rc on a child component if the parent has it already

Well idk your specifics but there isn't much harm in a refcell if that's the only way to ensure safety that's the only way to do it. It's just 1 branch

Learath2

Well idk your specifics but there isn't much harm in a refcell if that's the only way to ensure safety that's the only way to do it. It's just 1 branch

you are right and if you have a private field that is a refcell it's relatively safe

09:53

i also try to do it, if i use it. i guess i am in adventurer mode rn xd

09:56

the only problem is smth like this:

struct A { r: Rc<...> }
struct B { r: Rc<..>, a: A } // same rc as above

impl A { fn func() {r.borrow_mut().dosmth}}
impl B { fn func() {let borrowered = r.borrow_mut();
a.func(); // panic bcs a and b will borrow_mut at same time
}}


let b = B::...;
b.func();

(edited)

09:56

the 'inline lifetime could also also disallow being passed to a function etc.

09:57

well as said it only works under certain conditions, but it defs help to fuck up less in my case without having to have so many proc macros

10:01

now i am motivated to write test cases for my macro to find some of its limitations thanks for movation

Jupstar ✪

the only problem is smth like this:

struct A { r: Rc<...> }
struct B { r: Rc<..>, a: A } // same rc as above

impl A { fn func() {r.borrow_mut().dosmth}}
impl B { fn func() {let borrowered = r.borrow_mut();
a.func(); // panic bcs a and b will borrow_mut at same time
}}


let b = B::...;
b.func();

(edited)

Yeah this is suboptimal calling the functions while holding a borrow leading to a panic is bizarre feeling

its enforcing the borrow checker at runtime

Ryozuki

its enforcing the borrow checker at runtime

I'm more curious as to how you'd allow this pattern

whats the pattern i didnt read i was trying to fix my lalrpop pascal parser :/

10:15

and looking at a token Eof we can reduce to a CommaNoTrailing<"identifier"> but we can also reduce to a SemiColonNoTrailing<RecordSection>

10:15

im dying

Technically while a.func() is happening you are already holding a mut ref outside it so it panics, but technically it's sane. The second mut borrow is the only one in scope

10:16

Like a two phase borrow

10:17

You can get rid of the refcell too. I'm just curious how a seasoned rust veteran would structure it

10:19

@Jupstar ✪ is this components and cgameclient btw?

10:19

That's the sort of relationship those have

well you can do lot of stuff without Rc<RefCell>. sadly this can always increase complexity, by a lot, bcs u need to pass so much stuff around. Generally i think this isn't even bad, it's just that i want to have some modules be very easy to use

generally u want to structure ur code to avoud refcells at all

Learath2

@Jupstar ✪ is this components and cgameclient btw?

for me it's more the interaction with the graphics component by two or more components

Ryozuki

generally u want to structure ur code to avoud refcells at all

and still you use all these fancy libs that have a slim api. bcs they internally have Rc or Arcs

Jupstar ✪

the only problem is smth like this:

struct A { r: Rc<...> }
struct B { r: Rc<..>, a: A } // same rc as above

impl A { fn func() {r.borrow_mut().dosmth}}
impl B { fn func() {let borrowered = r.borrow_mut();
a.func(); // panic bcs a and b will borrow_mut at same time
}}


let b = B::...;
b.func();

(edited)

this code doesnt make sense, where do u get r in the B impl block

as said, it's a matter of simplicity

Yep that works too. So I guess the proper solution is for the components to not hold a ref to the graphics component

Jupstar ✪

and still you use all these fancy libs that have a slim api. bcs they internally have Rc or Arcs

what libs

Ryozuki

this code doesnt make sense, where do u get r in the B impl block

it's pseudo code

Ryozuki

what libs

i dunno, like 90% of the libs allow me to clone their instance of whatever

???

Jupstar ✪

i dunno, like 90% of the libs allow me to clone their instance of whatever

Yeah libs wrap their contexts in arcs

i hate arguments like that, u cant argue cuz its so vague

if you have a tokio runtime, u can just clone it and it's the same instance if you clone some sound lib, you can clone the runtime and it will just work

Anyway, why are you arguing? RefCell bad has nothing to do with Arc bad

yeah arc is kinda the way to share refs between threads

Learath2

Anyway, why are you arguing? RefCell bad has nothing to do with Arc bad

well Arc<Mutex> has the exact same problem xD

they want to allow send

Jupstar ✪

well Arc<Mutex> has the exact same problem xD

They don't require runtime borrow checking

true, it's even worse there

10:23

dead lock

well thats what uget when dealing with MT

10:23

but a arc alone wont deadlock u

10:23

its when u use a lock

10:24

consider refcell like a single thread lock

Ryozuki

but a arc alone wont deadlock u

yeah, but u cannot use arc and then write an API xd is that a read-only API or what? XD

but ucant block xd

Jupstar ✪

the only problem is smth like this:

struct A { r: Rc<...> }
struct B { r: Rc<..>, a: A } // same rc as above

impl A { fn func() {r.borrow_mut().dosmth}}
impl B { fn func() {let borrowered = r.borrow_mut();
a.func(); // panic bcs a and b will borrow_mut at same time
}}


let b = B::...;
b.func();

(edited)

Anyway can we not drift away? How would one solve this? Just establish a hierarchy so you only pass a reference down instead of keeping an Rc everywhere?

btw

10:25

u have try_borrow

10:25

iirc

10:25

u can borrow from the rc on a upper level and pass a plain ref down

Learath2

Anyway can we not drift away? How would one solve this? Just establish a hierarchy so you only pass a reference down instead of keeping an Rc everywhere?

i mean B can read the rc of A. and if the borrow_mut would be guaranteed inline, without side effects, it would not compile

10:25

so yes, that is kinda my plan

10:26

my problem isn't so much about that you have to redsign this call a bit. it can simply happen without you noticing it

10:26

that's what i dislike about it

Yeah, so I guess just don't have multiple references, pass it down instead

10:28

s/references/Rcs/

yep, but for the graphic instance it would suck to always pass it around. and i have a usecase where i potentially allow borrowing parts of the graphics api. so if 2 comps have the graphics cloned, this is problem xdd

use std::{cell::RefCell, rc::Rc};

struct A {
    r: Rc<RefCell<String>>,
}

struct B {
    r: Rc<RefCell<String>>,
    a: A,
}

impl A {
    pub fn funca(&self) {
        let _ = self.r.borrow_mut();
    }
}

impl B {
    pub fn funcb(&self) {
        let borrowed = self.r.borrow_mut();
        self.a.funca();
    }
}

fn main() {
    let r: Rc<RefCell<String>> = Default::default();
    let x = B {
        r: r.clone(),
        a: A { r },
    };

    x.funcb();
}

10:29

ok so this is the code

10:29

it panics on borrow mut

thanks for taking the time

sadly i dont have much time tho

10:30

i gotta go to office

10:30

and i need to cook my meal

10:30

XD

gl

Just bite the unsafepill

10:30

Who cares what the borrowchecker thinks. Who is he anyway

xdd

10:31

well i'd already be happy to make it harder to fuck up xD

Survival of the fittest

Learath2

Survival of the fittest

true, but if i am an overpowered cyborg, i've higher chances

10:35

so i tune myself

You know what would be cool? Some sort of "call stack local" variable

10:41

That way any frame that comes after a frame that mutably borrows something can share that borrow

use std::{cell::RefCell, rc::Rc};

struct A {
}

struct B {
    r: Rc<RefCell<String>>,
    a: A,
}

impl A {
    pub fn funca(&self, r: &mut String) {
        r.push('a');
    }
}

impl B {
    pub fn funcb(&self) {
        let mut borrowed = self.r.borrow_mut();
        self.a.funca(&mut borrowed);
    }
}

fn main() {
    let r: Rc<RefCell<String>> = Default::default();
    let x = B {
        r: r.clone(),
        a: A{},
    };

    x.funcb();
}

10:45

btw this is how i would do it

10:45

A simplydoesnt need to hold r

10:45

simply pass the mut ref when it needs on the fn

10:45

it compiles

10:45

now i go to work

10:47

this is why u can usually avoid refcells

10:47

on the second u dont need refcell for B either

10:47

they make life easier on some places and in some are needed ye

Ryozuki

btw this is how i would do it

Makes sense for this specific tiny example, but I think the point is that there are many As that maybe nested far deeper in hierarchy than in here

its hard to say without seeing the whole picture

And B may not even be the one that's directly holding A

Ryozuki

its hard to say without seeing the whole picture

Think CComponent and CGraphics

u have to structure things in rust like u would in rust

10:49

not like in java

10:50

this is why i find bevy amazing

10:50

bevy way is the way

10:50

i think its sensible to say, its better to have functions accept references to the objects u need and use them there instead of holding stuff in ur structs

10:51

limit the scope of ur references as much as possible

10:51

idk

Ryozuki

bevy way is the way

and how is it doing it?

the ECS

But ECS hardly applies to this situation

xd

10:52

is his design optimal in the first place

Well I guess entities could have a sprite component, which the gfx can call render on with a reference to gfx

https://docs.rs/bevy_ecs/latest/bevy_ecs/

bevy_ecs - Rust

Bevy ECS

Ryozuki

is his design optimal in the first place

i started with passing everything around. My point stands: it's simplicity vs compile time checks

design is not just passing all around

if you want automatic cleanup of resources on drop, you need a rc of that part of the graphics lib

but how u structure all ur code idk

else u need destroy manually

Ryozuki

but how u structure all ur code idk

yes, that's why i tryhard about this problem to not fuck up

designing things like this is part of the hard problems in programming

10:55

the other is MT

10:55

owo

i defs find my current solution MUCH easier to use, and for an end user easier to not fuck up but it 1. makes the graphics comp harder to implement 2. it still has some smaller holes for potential panics, which is dislike

Ryozuki

designing things like this is part of the hard problems in programming

You know where it isn't hard? C

10:56

No refcells, no Rcs, no borrowchecking. Just don't forget to free stuff bozo gigachad3

gigachad3

10:57

let's upgrade to c

Learath2

You know where it isn't hard? C

lots of segfaults

10:58

also he wants to abuse RAII

10:58

if he did manual freeing of resources he could just use a storage

RAII is for weak lazy men. Jupstar is big strong man

and it would be simple

10:58

in rust too

10:58

honestly i would probs go for some kind of storage

10:59

ecs kinda does that

Ryozuki

honestly i would probs go for some kind of storage

then the key/index to that storage can be invalid

11:00

i prefer the "if it can exists, it must exist" philosophy brownbear

brownbear

(edited)

Jupstar ✪

i defs find my current solution MUCH easier to use, and for an end user easier to not fuck up but it 1. makes the graphics comp harder to implement 2. it still has some smaller holes for potential panics, which is dislike

Q: Can't you make sure by some other means that all components die before the gfx one instead of an Rc? Isn't there a hierarchical owner of the gfx component that when dead it doesnt even make sense for the gfx component to live on?

Learath2

Q: Can't you make sure by some other means that all components die before the gfx one instead of an Rc? Isn't there a hierarchical owner of the gfx component that when dead it doesnt even make sense for the gfx component to live on?

so you want me to use a ptr?

I fail to see why one might want the components to be able to keep the gfx component alive if the client itself is gone e.g.

Learath2

I fail to see why one might want the components to be able to keep the gfx component alive if the client itself is gone e.g.

it don't want or need this actually

11:03

it's simply that resources hold a ref to the graphics comp for automatic cleanup, and i don't want to pass aroud graphics component every time

11:04

i introduced a concept of graphics programs, which should work as if it itself is a graphics implementation

11:04

e.g. the map rendering is not part of the graphics component anymore. engine & game are 100% split

Ah, hm that is actually a rather annoying steucture indeed

11:05

Too much thinking for me. I have a bag to pack, cya'll

Learath2

Q: Can't you make sure by some other means that all components die before the gfx one instead of an Rc? Isn't there a hierarchical owner of the gfx component that when dead it doesnt even make sense for the gfx component to live on?

maybe u could a way would be to have a struct wrapping the gfx with interior mutability and then u pass the outer struct by a plain non mut reference

11:05

rust will make sure the struct outlives conponents holding a ref to that struct

11:06

components just need to hold a ref

11:06

not a mut ref

11:06

aka use interior mutability but hiding the rc in a struct u share by ref

11:07

hmm

11:07

xd

11:07

ok idk

11:07

u then expose the gfx methods via &self

11:07

or whathever

xd

11:07

that's indeed what it does, no refcell is public

ur code was public

in 99% it just works. but sometimes gfx internal components talk to each other. Additionally i have at least one hole where i either pass a closure (harder to use) or have to make sure the graphics api is not in use already

Ryozuki

ur code was public

well it's very outdated. currently i code so much shit xD can't show this trash

https://austral-lang.org/

The Austral Programming Language

Austral is a systems programming language designed for simplicity, maintability and security.

11:12

Austral is a new systems programming language. It uses linear types to provide memory safety and capability-secure code, and is designed to be simple enough to be understood by a single person, with a focus on readability, maintainbility, and modularity

11:12

syntax is odd tho

11:12

ada like

Is there the concept of a call stack local variable in any language?

please invent one, i want to test it

I will craft a language one day. Even if it won't be used by anyone I want to experiment

what's a call-stack local variable?

11:20

you mean a global variable? visible to the call stack?

11:20

thread-local variable maybe?

Learath2

I will craft a language one day. Even if it won't be used by anyone I want to experiment

my company wants to make a lang

11:22

based on rust safety with go simplicity

11:23

inspired by the lang i sent

11:23

linear types

11:23

arent variables stored in the stack anyway

11:23

or register when possible

heinrich5991

you mean a global variable? visible to the call stack?

A global variable of sorts that would lie in some higher stack frame. Maybe like an export of sorts. With visibility only within that chain of calls until the function who initially exported it returns

11:24

Like passing it down all the way but more ergonomic

that's the solution: no stack, no call frames => no problems

11:34

put everything in one big function xdd

how can a company just afford to make a lang

11:37

our company doesn't even want us to make our own playercontroller

that doesn't sound like a problem of money

it is if we need more than a week to make one

xd

btw we made our own anyway

11:46

Catxplosion

poggers2

and it sucks now

11:47

stair handling is broken kek

kek

and i dont have time to fix it

11:47

shouldve bought one or steal one

TsFreddie

it is if we need more than a week to make one

man i really wonder if your companies are really so horrible or if you exaggerate xd

Jupstar ✪

man i really wonder if your companies are really so horrible or if you exaggerate xd

definitely exaggerate

xD

but also not?

Jupstar ✪

that's the solution: no stack, no call frames => no problems

YES

it sounds bad

Jupstar ✪

man i really wonder if your companies are really so horrible or if you exaggerate xd

i just dont like working if you cant tell

11:50

and i think everyone is kinda stupid in the team. owo

owo

TsFreddie

and i think everyone is kinda stupid in the team. owo

owo

i feel that. the only difference is, that it includes myself

owo

you're better than me

vscode now supports floating windows

11:51

meaning u can move a opened file to second display

Ryozuki

vscode now supports floating windows

omg

ye, thats cool

biggest feature

11:51

requested since years

now i just need 2 screens so it's worth it

i want the sidebar to float tho

owo

float this

cuz the explorer takes half of my vertical screen

TsFreddie

i want the sidebar to float tho

you can make the sidebar be a bottombar

can you now. havent used vscode for quite a while

u can drag the icon to some places xd

isn't explorer fixed to be on the side.

11:55

anyway i better check myself

u gotta drag the explorer icon, then it's not fixed

any neovim enjoyers?

i know enough vim to close it

11:57

kek

11:58

also i know enough to mess my colleague when one of them actually uses a vim plugin in vscode. i be hitting that I key quicker than him wanting to explain it to me. (edited)

I love % and _

i love changing my text editor alternatives to not use vim

i gotta get my settings back but im lazy af

<ChillerDragon> @MilkeeyCat what is % and _ and do they work in vanilla vim too?

ws-client

<ChillerDragon> @MilkeeyCat what is % and _ and do they work in vanilla vim too?

Do you use vim?

13:52

_ goes to first non empty character and % goes to.. eeeh. Opposite character. Like you have { hdhfus } if ur cursor under { and u press % it goes to }

#1234

https://github.com/ddnet/ddnet/issues/1234

kill dummy · Issue #1234 · ddnet/ddnet

for even more dummy control AllTheHaxx/AllTheHaxx@91394cb

rest in piece

Windows

brownbear

Image attachment

Sedonya

Windows

brownbear

Checked out libs?

Yes

14:30

Everything is in place on GitHub and on my PC

14:30

I also tried to fix it with this

Image attachment

14:31

I also wrote git submodule update --init --recursive

Sedonya

I also tried to fix it with this

Maybe that is the problem

14:32

I never tested it with the sdk xd

14:32

It must be in your path and stuff

14:33

Since our CI isn't failing it should work on Windows

Jupstar ✪

Since our CI isn't failing it should work on Windows

I'm compiling dfng <3

Sedonya

I'm compiling dfng <3

Then you can also use -DCLIENT=OFF for cmake, i guess

thx

Jupstar ✪

Then you can also use -DCLIENT=OFF for cmake, i guess

Image attachment

Sedonya

Click to see attachment 🖼️

To me that looks like a clear indicator that libs are not checked out

maybe xd

14:49

but I didn't change anything in the repository

I dunno. Just download the ones from ddnet

14:49

And put them there

14:49

It should: tm: work

I solved the problem with connecting to my server, the problem was that I have an ovh anti-ddos and because of this, no one can log in until they establish a direct connection to the server (i.e. until they add it to the hosts file (maybe))

[ddnet-web:master] 1 new commit

baecdb8 Add 100€ donation by Gummibaer12345 - def-

1

@Gummibaer12345 Thank you!

deen

@Gummibaer12345 Thank you!

:3 Merry christmas to you guys (edited)

owo

1

only 45€ missing until 2023 is completely funded!

Learath2

A global variable of sorts that would lie in some higher stack frame. Maybe like an export of sorts. With visibility only within that chain of calls until the function who initially exported it returns

sounds like a thread-local Option<> to me

-StormAh~

Linear interpolation

wait arent tees already LERPed?

Just a tad too large in scope no?

well thread locals are not readable by other threads xd (edited)

18:43

depends if u want to support this, or if that is out of your stack stack frame

18:43

@Learath2 do you like coroutines?

Voxel

wait arent tees already LERPed?

Uhh, are they?

I like the idea of them, but I honestly dont ever think in terms of them nor do many languages support them, so I rarely get to use them

18:48

Maybe if I learn some go

-StormAh~

Uhh, are they?

yes, otherwise the maximum would be 50 frames per second

18:53

raibow tees

small typo

intratick

-StormAh~

Uhh, are they?

wait then what IS lerped?

whats radmin doing on ur website? (edited)

Image attachment

19:02

@-StormAh~

MilkeeyCat

whats radmin doing on ur website? (edited)

Radmin template

19:05

justatest

️

Voxel

wait then what IS lerped?

Means unlocked feets, hammer etc

19:16

That what you can see on this video

19:16

https://cdn.discordapp.com/attachments/295908390956433410/1186106431762604112/Disability_2023-12-18_02-39-07.mp4?ex=65920ab2&is=657f95b2&hm=7b6b0b52f6d2f37bed6ca27f5124009a9ad8781d7a298c7167e583635858df36&

oh thaat

mid map

isnt it just the feet and hammer lagging behind 1 frame

-StormAh~

https://cdn.discordapp.com/attachments/295908390956433410/1186106431762604112/Disability_2023-12-18_02-39-07.mp4?ex=65920ab2&is=657f95b2&hm=7b6b0b52f6d2f37bed6ca27f5124009a9ad8781d7a298c7167e583635858df36&

this feature is not original btw

-StormAh~

Means unlocked feets, hammer etc

And this have a lot of bugs, cuz I programmed this troll

troll

https://www.youtube.com/watch?v=0dq1BpvjWEE

Teeworlds Goresworld clientmod

19:21

look my vid from 8 years ago

19:21

their feet

Ryozuki

this feature is not original btw

Ye, this was taken from goreworlds to my client, and from my client to storm client

Ryozuki

this feature is not original btw

Yeah i saw that somewhere already

19:21

However you can just turn it off

the blood is funny

pepesmash

1

monkaS

1

Mʎɹ シ

Ye, this was taken from goreworlds to my client, and from my client to storm client

github

hehehe

i gotta make an offline client so i can just fuck around

19:23

i love the teeworlds engine

19:23

has so much potential

I love teewars engine, has so much potential

I love teeworlds

19:24

That's all i can say

i love rust

19:24

rustworlds*

I love asm

im blocking you

Binworlds*

1 blocked message (edited)

Blockworlds

not like we interact much lately xD

i am at peace now

good, i can say linux without u answering windows

19:26

:3

19:27

https://andrewkchan.dev/posts/fire.html

-StormAh~

Means unlocked feets, hammer etc

maybe "fresh animations"

Patiga

maybe "fresh animations"

Fair, guess i have to rename it

Lagging animations

https://www.jpl.nasa.gov/news/nasas-tech-demo-streams-first-video-from-deep-space-via-laser

NASA’s Tech Demo Streams First Video From Deep Space via Laser

The video, featuring a cat named Taters, was sent back from nearly 19 million miles away by NASA’s laser communications demonstration, marking a historic milestone.

1

19:27

nasa sent a cat video

19:27

to space

19:27

based

Mʎɹ シ

Lagging animations

cursed*

Patiga

maybe "fresh animations"

yea

call it "cursed_animations_ported_from_Goresworld_to_toilet_to_stormax" (edited)

tbh if it was less dramatic itd be cool

@Learath2 did u know ocaml has += for type definitions

BlaiZephyr | meloƞ

call it "cursed_animations_ported_from_Goresworld_to_toilet_to_stormax" (edited)

Imagine how config variables will be named justatest

justatest

Ryozuki

@Learath2 did u know ocaml has += for type definitions

I barely knew ocaml existed

camel

https://v2.ocaml.org/manual/extensiblevariants.html

Objective Camel!

Learath2

I barely knew ocaml existed

honestly ocaml is big

19:34

its used to make compilers

19:34

i havent learned it tho

19:34

but the bad thing is it has circular deps problem

I would make my compiler in C, don't need no camel

xd

Learath2

I would make my compiler in C, don't need no camel

you keep on writing rust wrong smh

2

@Learath2 its rly rly easy to make a compilere in ocaml

19:35

i think it falls nicely

19:35

rust was originally made with ocaml

19:35

llvm has oficial bindings in ocaml

BlaiZephyr | meloƞ

you keep on writing rust wrong smh

The rust lobby has arrived

xd

peepoShy

the unfunniest group of people ever

i mean i dont wanna brag, but i not only enjoy rust... i use arch btw!

ok yeah thats my push thank you

gentoo here

justatest

1

did i just get blocked ._.

why do u care

true

the holy path to rust has obstacles

19:38

now join the church of memory safety

19:39

and confess (tell me ur unsafe uses) to me in the confession box

19:39

justatest

Voxel just gone

https://en.wikipedia.org/wiki/Confession_(religion)

19:39

XD

What??

not everyone can be as superior as us rust enjoyers

BlaiZephyr | meloƞ

i mean i dont wanna brag, but i not only enjoy rust... i use arch btw!

You said rust?

Image attachment

witzig witzig

BlaiZephyr | meloƞ

did i just get blocked ._.

Arch is old news. All the real cool people use gentoo now

Jupstar ✪

witzig witzig

mentioning zig is a sin here

19:44

forgive me Ryozuki for i have sinned

[ddnet/ddnet] Pull request opened: #7684 Clear console selection only when scroll position is changed

The selection is only cleared because it would be incorrect after scrolling, but it doesn't need to be cleared if the scroll position does not change, e.g. when pressing Home while already at the top of the backlog.

Checklist

[X] Tested the change ingame
[ ] Provided screenshots if it is a visual change
[ ] Tested in combination with possibly related configuration options
[ ] Written a unit test (especially base/) or added coverage to integration test
[ ] Considered pos...

@MilkeeyCat _ goes to start of line and % does nothing gg

Image attachment

xd

xd

isnt zig the new shit that will replace rust?

no it has no memor safety

20:38

its hipster C

wot no memory safety?

20:38

thats so 1999

yeah

ChillerDragon

@MilkeeyCat _ goes to start of line and % does nothing gg

Time to try neovim

i tried in neovim too

20:39

same result

Wat

german keyboard layout :p

20:39

20:39

It's default motions, they have to work xd

not on my machine

Works on ukrainian, russian, czech and english layouts

i use f<space> for those scenarios i guess

20:40

or f,

20:40

germany issue then

XD

20:42

Do u have config for ur vim on gh?

20:47

chillerdragon: was ur cursor at '{' char when u were pressing %?

Image attachment

21:01

21:01

@Ryozuki @deen

xd

Jupstar ✪

well thread locals are not readable by other threads xd (edited)

but a callstack usually lives in one thread only, no?

Learath2

I like the idea of them, but I honestly dont ever think in terms of them nor do many languages support them, so I rarely get to use them

rust too, no?

heinrich5991

but a callstack usually lives in one thread only, no?

sounded more like a var that lives on the stack somewhere

Cellegen

Click to see attachment 🖼️

instead of donating 100 euros you should donate 1 euro 100 times and add a different name each time

21:05

troll

Cellegen

Click to see attachment 🖼️

real pros let the girl die

21:05

Learath2

I would make my compiler in C, don't need no camel

C seems like the wrong choice, given no ADTs

cyberFighter

instead of donating 100 euros you should donate 1 euro 100 times and add a different name each time

fuck missed opportunity

21:06

is there a specific reasons /showothers only works on the client you activate it on?, if its off and i set it on with /showothers, and switch to dummy, its disabled there

there's a technical reason, but no concrete design reason, I guess

heinrich5991

rust too, no?

Doesn’t rust only have them in nightly?

heinrich5991

C seems like the wrong choice, given no ADTs

Well I was half jesting. The only reason I would even consider C for a compiler is because something so complex I probably should write in the language I’m most familiar with

Learath2

Doesn’t rust only have them in nightly?

ah, futures are not co-routine-y enough?

22:12

yes

[ddnet-web:master] 3 new commits

4e76ba8 Add another 44€ donation by Cellegen - def- b58a9d5 Add 45€ donation by Zwelf - def- 397893a Remove donation link - def-

@Cellegen Thanks again for the second donation in 2 days!

22:30

@Zwelf Thanks for the donation, you two filled up the missing 45 € kind of at once

1

Image attachment

[ddnet-web:master] 1 new commit

a17881c Fix POL server costs - def-

22:34

[ddnet-web:master] 1 new commit

7645b32 Fix funding completed for 2023 - def-

completely funded

poggers2

ChillerDragon/dotfiles

Replying to @MilkeeyCat Do u have config for ur vim on gh?

22:54

My cursor was in a word I had no { only spaces I thought it also jumps to spaces

22:54

Do I need a literal { ?

damn, didn't think it was this easy to leak chatGPT training data

23:05

https://www.zdnet.com/article/chatgpt-can-leak-source-data-violate-privacy-says-googles-deepmind/ (edited)

heinrich5991

ah, futures are not co-routine-y enough?

Oh, hm are they really comparable? I guess a Stream is kinda close but it still lacks the ability to yield to a specific destination

Learath2

Oh, hm are they really comparable? I guess a Stream is kinda close but it still lacks the ability to yield to a specific destination

can you give a more concrete example? I can .await a future to yield to a specific destination? I guess I don't really know what coroutines are

heinrich5991

can you give a more concrete example? I can .await a future to yield to a specific destination? I guess I don't really know what coroutines are

Symmetric coroutines allow the callee to dictate where to yield to

I only know them in theory aswell, as I said not many languages have them and thus I never really think in terms of them so idk how useful a symmetric coroutine is

23:29

Instead of just yield 5 you get something like yield coro_b 5

@voxel ?

23:56

he gone

23:57

oh you made him leave (edited)

23:58

you guys suck

Ewan

oh you made him leave (edited)

he is still here, you just have a skill issue in hiliting people

Exported 502 message(s)