WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:13.030 align:start position:0% [Music] 00:00:13.030 --> 00:00:13.040 align:start position:0% 00:00:13.040 --> 00:00:16.870 align:start position:0% okay<00:00:14.040> good<00:00:14.240> day<00:00:14.879> my<00:00:15.080> name<00:00:15.360> is<00:00:15.719> Tony<00:00:16.199> I<00:00:16.320> work<00:00:16.600> at 00:00:16.870 --> 00:00:16.880 align:start position:0% okay good day my name is Tony I work at 00:00:16.880 --> 00:00:19.950 align:start position:0% okay good day my name is Tony I work at the<00:00:17.279> nomic<00:00:17.840> foundation<00:00:18.439> in<00:00:18.640> applied 00:00:19.950 --> 00:00:19.960 align:start position:0% the nomic foundation in applied 00:00:19.960 --> 00:00:23.710 align:start position:0% the nomic foundation in applied research<00:00:20.960> uh<00:00:21.080> I<00:00:21.160> was<00:00:21.439> previously<00:00:22.359> a<00:00:22.720> co-lead 00:00:23.710 --> 00:00:23.720 align:start position:0% research uh I was previously a co-lead 00:00:23.720 --> 00:00:26.269 align:start position:0% research uh I was previously a co-lead on<00:00:24.000> the<00:00:24.080> slang<00:00:24.880> project<00:00:25.439> and<00:00:25.560> it's<00:00:25.720> in<00:00:25.960> this 00:00:26.269 --> 00:00:26.279 align:start position:0% on the slang project and it's in this 00:00:26.279 --> 00:00:28.070 align:start position:0% on the slang project and it's in this capacity<00:00:26.880> that<00:00:27.039> I'm<00:00:27.279> going<00:00:27.359> to<00:00:27.560> speak<00:00:27.760> to<00:00:27.920> you 00:00:28.070 --> 00:00:28.080 align:start position:0% capacity that I'm going to speak to you 00:00:28.080 --> 00:00:30.150 align:start position:0% capacity that I'm going to speak to you today 00:00:30.150 --> 00:00:30.160 align:start position:0% today 00:00:30.160 --> 00:00:32.790 align:start position:0% today I<00:00:30.240> have<00:00:30.359> a<00:00:30.560> fantastic<00:00:31.359> job<00:00:31.880> working<00:00:32.279> with 00:00:32.790 --> 00:00:32.800 align:start position:0% I have a fantastic job working with 00:00:32.800 --> 00:00:35.869 align:start position:0% I have a fantastic job working with excellent<00:00:33.320> people<00:00:34.200> at<00:00:34.360> nomc<00:00:34.920> nomic<00:00:35.360> is<00:00:35.440> a 00:00:35.869 --> 00:00:35.879 align:start position:0% excellent people at nomc nomic is a 00:00:35.879 --> 00:00:39.830 align:start position:0% excellent people at nomc nomic is a nonprofit<00:00:36.879> and<00:00:37.079> our<00:00:37.320> number<00:00:37.719> one<00:00:38.719> core<00:00:39.079> value 00:00:39.830 --> 00:00:39.840 align:start position:0% nonprofit and our number one core value 00:00:39.840 --> 00:00:43.029 align:start position:0% nonprofit and our number one core value is<00:00:40.239> kindness<00:00:40.719> and<00:00:40.840> we<00:00:40.960> live<00:00:41.200> this<00:00:41.440> every<00:00:42.039> day 00:00:43.029 --> 00:00:43.039 align:start position:0% is kindness and we live this every day 00:00:43.039 --> 00:00:45.150 align:start position:0% is kindness and we live this every day and<00:00:43.160> we<00:00:43.320> are<00:00:43.559> hiring<00:00:44.399> there's<00:00:44.600> meant<00:00:44.760> to<00:00:44.879> be<00:00:45.000> a 00:00:45.150 --> 00:00:45.160 align:start position:0% and we are hiring there's meant to be a 00:00:45.160 --> 00:00:47.189 align:start position:0% and we are hiring there's meant to be a QR<00:00:45.480> code<00:00:45.680> at<00:00:45.800> the<00:00:45.879> end<00:00:46.039> of<00:00:46.199> my<00:00:46.320> slides<00:00:46.760> but<00:00:47.039> I'm 00:00:47.189 --> 00:00:47.199 align:start position:0% QR code at the end of my slides but I'm 00:00:47.199 --> 00:00:50.910 align:start position:0% QR code at the end of my slides but I'm afraid<00:00:47.719> it<00:00:47.879> didn't<00:00:48.199> make<00:00:48.719> it<00:00:49.719> uh<00:00:50.480> and<00:00:50.719> I<00:00:50.800> want 00:00:50.910 --> 00:00:50.920 align:start position:0% afraid it didn't make it uh and I want 00:00:50.920 --> 00:00:53.630 align:start position:0% afraid it didn't make it uh and I want to<00:00:51.120> give<00:00:51.559> heartfelt<00:00:52.239> thanks<00:00:52.600> to<00:00:53.320> the 00:00:53.630 --> 00:00:53.640 align:start position:0% to give heartfelt thanks to the 00:00:53.640 --> 00:00:57.310 align:start position:0% to give heartfelt thanks to the co-founders<00:00:54.320> of<00:00:54.520> nomic<00:00:55.520> p<00:00:56.199> and<00:00:56.559> Fran<00:00:57.039> for 00:00:57.310 --> 00:00:57.320 align:start position:0% co-founders of nomic p and Fran for 00:00:57.320 --> 00:01:00.470 align:start position:0% co-founders of nomic p and Fran for creating<00:00:57.800> and<00:00:58.120> maintaining<00:00:59.120> such<00:00:59.359> an<00:01:00.039> amazing 00:01:00.470 --> 00:01:00.480 align:start position:0% creating and maintaining such an amazing 00:01:00.480 --> 00:01:02.270 align:start position:0% creating and maintaining such an amazing place<00:01:00.719> to 00:01:02.270 --> 00:01:02.280 align:start position:0% place to 00:01:02.280 --> 00:01:06.070 align:start position:0% place to work<00:01:03.559> so<00:01:04.559> today<00:01:04.839> we're<00:01:04.960> going<00:01:05.080> to<00:01:05.280> explore<00:01:05.760> the 00:01:06.070 --> 00:01:06.080 align:start position:0% work so today we're going to explore the 00:01:06.080 --> 00:01:08.870 align:start position:0% work so today we're going to explore the slang<00:01:06.600> query<00:01:07.000> API<00:01:07.640> which<00:01:07.759> is<00:01:07.960> a<00:01:08.080> new<00:01:08.240> feature 00:01:08.870 --> 00:01:08.880 align:start position:0% slang query API which is a new feature 00:01:08.880 --> 00:01:11.510 align:start position:0% slang query API which is a new feature which<00:01:09.560> makes<00:01:09.880> working<00:01:10.280> with<00:01:10.520> solidity<00:01:11.119> code 00:01:11.510 --> 00:01:11.520 align:start position:0% which makes working with solidity code 00:01:11.520 --> 00:01:13.990 align:start position:0% which makes working with solidity code surprisingly<00:01:12.680> straightforward<00:01:13.680> and<00:01:13.799> now 00:01:13.990 --> 00:01:14.000 align:start position:0% surprisingly straightforward and now 00:01:14.000 --> 00:01:15.950 align:start position:0% surprisingly straightforward and now this<00:01:14.080> is<00:01:14.200> not<00:01:14.360> a<00:01:14.560> tutorial<00:01:15.240> so<00:01:15.520> some<00:01:15.680> of<00:01:15.799> the 00:01:15.950 --> 00:01:15.960 align:start position:0% this is not a tutorial so some of the 00:01:15.960 --> 00:01:18.230 align:start position:0% this is not a tutorial so some of the details<00:01:16.320> have<00:01:16.479> been<00:01:16.840> omitted<00:01:17.560> you<00:01:17.720> can't<00:01:18.000> copy 00:01:18.230 --> 00:01:18.240 align:start position:0% details have been omitted you can't copy 00:01:18.240 --> 00:01:19.830 align:start position:0% details have been omitted you can't copy and<00:01:18.439> paste<00:01:18.720> any<00:01:18.880> of<00:01:19.000> the<00:01:19.159> code<00:01:19.479> that<00:01:19.600> I'm<00:01:19.759> going 00:01:19.830 --> 00:01:19.840 align:start position:0% and paste any of the code that I'm going 00:01:19.840 --> 00:01:23.230 align:start position:0% and paste any of the code that I'm going to<00:01:20.000> be<00:01:20.520> providing<00:01:21.520> it's<00:01:22.079> just<00:01:22.520> so<00:01:22.799> that<00:01:23.000> you 00:01:23.230 --> 00:01:23.240 align:start position:0% to be providing it's just so that you 00:01:23.240 --> 00:01:25.990 align:start position:0% to be providing it's just so that you can<00:01:23.720> well<00:01:23.960> I'm<00:01:24.119> hoping<00:01:24.360> to<00:01:24.600> inspire<00:01:25.079> you<00:01:25.799> so 00:01:25.990 --> 00:01:26.000 align:start position:0% can well I'm hoping to inspire you so 00:01:26.000 --> 00:01:27.710 align:start position:0% can well I'm hoping to inspire you so that<00:01:26.200> you<00:01:26.560> uh<00:01:26.680> go<00:01:26.799> and<00:01:27.000> find<00:01:27.159> out<00:01:27.320> some<00:01:27.479> more 00:01:27.710 --> 00:01:27.720 align:start position:0% that you uh go and find out some more 00:01:27.720 --> 00:01:30.590 align:start position:0% that you uh go and find out some more details<00:01:28.680> okay<00:01:28.880> so<00:01:29.400> 20<00:01:29.680> minutes 00:01:30.590 --> 00:01:30.600 align:start position:0% details okay so 20 minutes 00:01:30.600 --> 00:01:32.630 align:start position:0% details okay so 20 minutes is<00:01:30.720> a<00:01:30.840> bit<00:01:30.960> of<00:01:31.079> a<00:01:31.200> Sprint<00:01:32.079> so<00:01:32.280> I'm<00:01:32.360> going<00:01:32.479> to 00:01:32.630 --> 00:01:32.640 align:start position:0% is a bit of a Sprint so I'm going to 00:01:32.640 --> 00:01:34.990 align:start position:0% is a bit of a Sprint so I'm going to speed<00:01:32.960> up<00:01:33.360> let's 00:01:34.990 --> 00:01:35.000 align:start position:0% speed up let's 00:01:35.000 --> 00:01:39.149 align:start position:0% speed up let's go<00:01:36.000> okay<00:01:36.159> so<00:01:36.320> what<00:01:36.439> is<00:01:36.880> slang<00:01:37.880> so<00:01:38.119> slang's<00:01:38.680> our 00:01:39.149 --> 00:01:39.159 align:start position:0% go okay so what is slang so slang's our 00:01:39.159 --> 00:01:42.590 align:start position:0% go okay so what is slang so slang's our solidity<00:01:39.759> compiler<00:01:40.360> Library<00:01:41.200> it's<00:01:41.960> uh 00:01:42.590 --> 00:01:42.600 align:start position:0% solidity compiler Library it's uh 00:01:42.600 --> 00:01:45.910 align:start position:0% solidity compiler Library it's uh basically<00:01:43.600> a<00:01:44.360> developer<00:01:44.880> tool<00:01:45.320> that<00:01:45.439> enables 00:01:45.910 --> 00:01:45.920 align:start position:0% basically a developer tool that enables 00:01:45.920 --> 00:01:49.389 align:start position:0% basically a developer tool that enables you<00:01:46.119> to<00:01:46.320> write<00:01:46.560> better<00:01:47.040> tools<00:01:48.040> it<00:01:48.280> passes<00:01:49.119> and 00:01:49.389 --> 00:01:49.399 align:start position:0% you to write better tools it passes and 00:01:49.399 --> 00:01:52.709 align:start position:0% you to write better tools it passes and analyzes<00:01:50.000> solidity<00:01:50.520> code<00:01:50.840> from<00:01:51.640> version 00:01:52.709 --> 00:01:52.719 align:start position:0% analyzes solidity code from version 00:01:52.719 --> 00:01:55.590 align:start position:0% analyzes solidity code from version 0.4.1<00:01:53.719> to<00:01:54.280> the<00:01:54.439> latest 00:01:55.590 --> 00:01:55.600 align:start position:0% 0.4.1 to the latest 00:01:55.600 --> 00:01:58.950 align:start position:0% 0.4.1 to the latest 0.8<00:01:56.600> which<00:01:56.719> is<00:01:56.920> basically<00:01:57.479> all<00:01:57.680> of<00:01:57.880> the<00:01:58.399> cility 00:01:58.950 --> 00:01:58.960 align:start position:0% 0.8 which is basically all of the cility 00:01:58.960 --> 00:02:00.670 align:start position:0% 0.8 which is basically all of the cility code<00:01:59.240> that<00:01:59.360> is 00:02:00.670 --> 00:02:00.680 align:start position:0% code that is 00:02:00.680 --> 00:02:04.950 align:start position:0% code that is live<00:02:01.680> uh<00:02:01.840> our<00:02:02.039> focus<00:02:02.399> is<00:02:02.560> on<00:02:02.880> correctness<00:02:03.799> and 00:02:04.950 --> 00:02:04.960 align:start position:0% live uh our focus is on correctness and 00:02:04.960 --> 00:02:07.230 align:start position:0% live uh our focus is on correctness and convenience<00:02:05.960> uh<00:02:06.079> we're<00:02:06.280> about<00:02:06.479> to<00:02:06.680> release 00:02:07.230 --> 00:02:07.240 align:start position:0% convenience uh we're about to release 00:02:07.240 --> 00:02:09.229 align:start position:0% convenience uh we're about to release version<00:02:07.600> one<00:02:08.319> which<00:02:08.479> covers<00:02:08.800> the<00:02:08.920> typical 00:02:09.229 --> 00:02:09.239 align:start position:0% version one which covers the typical 00:02:09.239 --> 00:02:12.550 align:start position:0% version one which covers the typical front<00:02:09.479> end<00:02:09.720> features<00:02:10.360> of<00:02:10.560> a<00:02:11.160> compiler<00:02:12.160> and<00:02:12.319> our 00:02:12.550 --> 00:02:12.560 align:start position:0% front end features of a compiler and our 00:02:12.560 --> 00:02:14.830 align:start position:0% front end features of a compiler and our main<00:02:13.080> objective<00:02:13.640> as<00:02:13.720> I<00:02:13.879> said<00:02:14.160> is<00:02:14.319> to<00:02:14.519> enable 00:02:14.830 --> 00:02:14.840 align:start position:0% main objective as I said is to enable 00:02:14.840 --> 00:02:16.910 align:start position:0% main objective as I said is to enable you<00:02:14.959> to<00:02:15.120> develop<00:02:15.760> better 00:02:16.910 --> 00:02:16.920 align:start position:0% you to develop better 00:02:16.920 --> 00:02:20.949 align:start position:0% you to develop better tools<00:02:17.920> uh<00:02:18.080> slang<00:02:18.480> has<00:02:18.599> a<00:02:18.840> radical<00:02:19.840> open<00:02:20.840> uh 00:02:20.949 --> 00:02:20.959 align:start position:0% tools uh slang has a radical open uh 00:02:20.959 --> 00:02:23.309 align:start position:0% tools uh slang has a radical open uh declarative<00:02:21.599> met 00:02:23.309 --> 00:02:23.319 align:start position:0% declarative met 00:02:23.319 --> 00:02:25.910 align:start position:0% declarative met architecture<00:02:24.319> slang's<00:02:24.920> a<00:02:25.160> error<00:02:25.480> correcting 00:02:25.910 --> 00:02:25.920 align:start position:0% architecture slang's a error correcting 00:02:25.920 --> 00:02:28.150 align:start position:0% architecture slang's a error correcting compiler<00:02:26.360> so<00:02:26.519> it<00:02:26.680> always<00:02:27.080> produces<00:02:27.560> output 00:02:28.150 --> 00:02:28.160 align:start position:0% compiler so it always produces output 00:02:28.160 --> 00:02:31.350 align:start position:0% compiler so it always produces output even<00:02:28.400> if<00:02:28.519> you've<00:02:28.720> got<00:02:28.879> source<00:02:29.280> code<00:02:29.519> errors 00:02:31.350 --> 00:02:31.360 align:start position:0% even if you've got source code errors 00:02:31.360 --> 00:02:33.150 align:start position:0% even if you've got source code errors uh<00:02:31.519> a<00:02:31.720> key<00:02:31.920> feature<00:02:32.280> of<00:02:32.400> slang<00:02:32.800> which<00:02:32.920> is<00:02:33.040> what 00:02:33.150 --> 00:02:33.160 align:start position:0% uh a key feature of slang which is what 00:02:33.160 --> 00:02:35.550 align:start position:0% uh a key feature of slang which is what we're<00:02:33.360> here<00:02:33.480> to<00:02:33.680> talk<00:02:33.920> about<00:02:34.760> is<00:02:34.920> its<00:02:35.200> query 00:02:35.550 --> 00:02:35.560 align:start position:0% we're here to talk about is its query 00:02:35.560 --> 00:02:38.710 align:start position:0% we're here to talk about is its query API<00:02:35.959> for<00:02:36.160> code 00:02:38.710 --> 00:02:38.720 align:start position:0% 00:02:38.720 --> 00:02:41.149 align:start position:0% analysis<00:02:39.720> so<00:02:39.959> compiler<00:02:40.400> front<00:02:40.599> ends<00:02:40.879> fall 00:02:41.149 --> 00:02:41.159 align:start position:0% analysis so compiler front ends fall 00:02:41.159 --> 00:02:43.390 align:start position:0% analysis so compiler front ends fall into<00:02:41.400> two<00:02:41.640> main<00:02:41.959> categories<00:02:42.879> there<00:02:42.959> are<00:02:43.200> those 00:02:43.390 --> 00:02:43.400 align:start position:0% into two main categories there are those 00:02:43.400 --> 00:02:44.869 align:start position:0% into two main categories there are those that<00:02:43.599> produce<00:02:43.920> what's<00:02:44.120> called<00:02:44.400> concrete 00:02:44.869 --> 00:02:44.879 align:start position:0% that produce what's called concrete 00:02:44.879 --> 00:02:46.990 align:start position:0% that produce what's called concrete syntax<00:02:45.319> trees<00:02:45.760> and<00:02:45.959> then<00:02:46.120> produce<00:02:46.800> an 00:02:46.990 --> 00:02:47.000 align:start position:0% syntax trees and then produce an 00:02:47.000 --> 00:02:49.309 align:start position:0% syntax trees and then produce an abstract<00:02:47.440> syntax<00:02:47.840> tree<00:02:48.120> from<00:02:48.360> that<00:02:49.080> and<00:02:49.200> there 00:02:49.309 --> 00:02:49.319 align:start position:0% abstract syntax tree from that and there 00:02:49.319 --> 00:02:51.589 align:start position:0% abstract syntax tree from that and there are<00:02:49.480> those<00:02:49.680> that<00:02:49.840> produce<00:02:50.239> abstract<00:02:50.680> syntax 00:02:51.589 --> 00:02:51.599 align:start position:0% are those that produce abstract syntax 00:02:51.599 --> 00:02:52.790 align:start position:0% are those that produce abstract syntax trees 00:02:52.790 --> 00:02:52.800 align:start position:0% trees 00:02:52.800 --> 00:02:54.910 align:start position:0% trees directly<00:02:53.800> uh<00:02:54.000> so<00:02:54.239> what's<00:02:54.440> the<00:02:54.599> difference 00:02:54.910 --> 00:02:54.920 align:start position:0% directly uh so what's the difference 00:02:54.920 --> 00:02:58.229 align:start position:0% directly uh so what's the difference between<00:02:55.640> concrete<00:02:56.200> syntax<00:02:57.200> and<00:02:57.800> Abstract 00:02:58.229 --> 00:02:58.239 align:start position:0% between concrete syntax and Abstract 00:02:58.239 --> 00:03:01.110 align:start position:0% between concrete syntax and Abstract syntax<00:02:58.800> well<00:02:59.440> concrete<00:03:00.040> syntax<00:03:00.800> as<00:03:00.920> you<00:03:01.000> can 00:03:01.110 --> 00:03:01.120 align:start position:0% syntax well concrete syntax as you can 00:03:01.120 --> 00:03:03.070 align:start position:0% syntax well concrete syntax as you can see<00:03:01.360> on<00:03:01.519> this<00:03:01.720> slide<00:03:02.400> is<00:03:02.519> a<00:03:02.680> complete 00:03:03.070 --> 00:03:03.080 align:start position:0% see on this slide is a complete 00:03:03.080 --> 00:03:05.030 align:start position:0% see on this slide is a complete representation<00:03:03.720> of<00:03:03.840> the<00:03:03.920> source<00:03:04.280> code<00:03:04.879> it 00:03:05.030 --> 00:03:05.040 align:start position:0% representation of the source code it 00:03:05.040 --> 00:03:06.990 align:start position:0% representation of the source code it includes<00:03:05.519> every<00:03:05.879> character<00:03:06.480> every<00:03:06.680> bit<00:03:06.799> of 00:03:06.990 --> 00:03:07.000 align:start position:0% includes every character every bit of 00:03:07.000 --> 00:03:10.149 align:start position:0% includes every character every bit of Whit<00:03:07.319> space<00:03:08.159> every<00:03:08.720> comment<00:03:09.720> it's<00:03:09.920> like 00:03:10.149 --> 00:03:10.159 align:start position:0% Whit space every comment it's like 00:03:10.159 --> 00:03:11.910 align:start position:0% Whit space every comment it's like having<00:03:10.560> as<00:03:10.640> I<00:03:10.799> say<00:03:11.080> like<00:03:11.280> having<00:03:11.440> the<00:03:11.560> full 00:03:11.910 --> 00:03:11.920 align:start position:0% having as I say like having the full 00:03:11.920 --> 00:03:13.910 align:start position:0% having as I say like having the full book<00:03:12.920> like<00:03:13.080> a 00:03:13.910 --> 00:03:13.920 align:start position:0% book like a 00:03:13.920 --> 00:03:17.589 align:start position:0% book like a PDF<00:03:14.920> uh<00:03:15.080> whereas<00:03:15.319> an<00:03:15.519> abstract<00:03:16.040> syntax 00:03:17.589 --> 00:03:17.599 align:start position:0% PDF uh whereas an abstract syntax 00:03:17.599 --> 00:03:20.910 align:start position:0% PDF uh whereas an abstract syntax tree<00:03:18.599> is<00:03:18.959> a<00:03:19.120> simplified<00:03:19.680> tree<00:03:20.040> representation 00:03:20.910 --> 00:03:20.920 align:start position:0% tree is a simplified tree representation 00:03:20.920 --> 00:03:24.070 align:start position:0% tree is a simplified tree representation so<00:03:21.159> it<00:03:21.280> doesn't<00:03:21.599> include<00:03:22.360> wh<00:03:22.680> space<00:03:23.159> and<00:03:23.480> equal 00:03:24.070 --> 00:03:24.080 align:start position:0% so it doesn't include wh space and equal 00:03:24.080 --> 00:03:27.550 align:start position:0% so it doesn't include wh space and equal signs<00:03:24.680> and<00:03:25.319> and<00:03:26.000> punctuation<00:03:27.000> it's<00:03:27.239> just<00:03:27.400> got 00:03:27.550 --> 00:03:27.560 align:start position:0% signs and and punctuation it's just got 00:03:27.560 --> 00:03:28.750 align:start position:0% signs and and punctuation it's just got the<00:03:27.720> essential 00:03:28.750 --> 00:03:28.760 align:start position:0% the essential 00:03:28.760 --> 00:03:31.429 align:start position:0% the essential details<00:03:29.840> like<00:03:30.000> if<00:03:30.080> you<00:03:30.159> were<00:03:30.319> reading<00:03:30.760> the<00:03:31.239> the 00:03:31.429 --> 00:03:31.439 align:start position:0% details like if you were reading the the 00:03:31.439 --> 00:03:33.030 align:start position:0% details like if you were reading the the plot<00:03:31.720> of<00:03:31.799> a<00:03:31.920> book<00:03:32.200> but<00:03:32.319> you<00:03:32.439> didn't<00:03:32.760> actually 00:03:33.030 --> 00:03:33.040 align:start position:0% plot of a book but you didn't actually 00:03:33.040 --> 00:03:34.550 align:start position:0% plot of a book but you didn't actually have<00:03:33.239> the 00:03:34.550 --> 00:03:34.560 align:start position:0% have the 00:03:34.560 --> 00:03:37.710 align:start position:0% have the text<00:03:35.560> so<00:03:35.920> here's<00:03:36.120> an<00:03:36.319> example<00:03:36.840> of<00:03:36.959> a<00:03:37.120> contract 00:03:37.710 --> 00:03:37.720 align:start position:0% text so here's an example of a contract 00:03:37.720 --> 00:03:40.550 align:start position:0% text so here's an example of a contract of<00:03:37.840> a<00:03:37.959> concrete<00:03:38.480> syntax<00:03:38.959> tree<00:03:39.959> so<00:03:40.159> we've<00:03:40.319> got<00:03:40.439> a 00:03:40.550 --> 00:03:40.560 align:start position:0% of a concrete syntax tree so we've got a 00:03:40.560 --> 00:03:43.309 align:start position:0% of a concrete syntax tree so we've got a simple<00:03:40.920> variable<00:03:41.400> declaration<00:03:42.319> here<00:03:43.080> and 00:03:43.309 --> 00:03:43.319 align:start position:0% simple variable declaration here and 00:03:43.319 --> 00:03:44.830 align:start position:0% simple variable declaration here and every<00:03:43.599> single<00:03:43.959> element<00:03:44.280> of<00:03:44.360> the<00:03:44.480> original 00:03:44.830 --> 00:03:44.840 align:start position:0% every single element of the original 00:03:44.840 --> 00:03:47.630 align:start position:0% every single element of the original source<00:03:45.200> is<00:03:45.400> represented<00:03:46.080> nothing<00:03:46.519> is<00:03:47.159> removed 00:03:47.630 --> 00:03:47.640 align:start position:0% source is represented nothing is removed 00:03:47.640 --> 00:03:48.390 align:start position:0% source is represented nothing is removed or 00:03:48.390 --> 00:03:48.400 align:start position:0% or 00:03:48.400 --> 00:03:50.789 align:start position:0% or simplified<00:03:49.400> now<00:03:49.720> this<00:03:49.840> is<00:03:50.239> different<00:03:50.519> from<00:03:50.680> an 00:03:50.789 --> 00:03:50.799 align:start position:0% simplified now this is different from an 00:03:50.799 --> 00:03:52.589 align:start position:0% simplified now this is different from an as<00:03:51.280> which<00:03:51.360> will<00:03:51.560> eliminate<00:03:52.000> some<00:03:52.120> of<00:03:52.280> these 00:03:52.589 --> 00:03:52.599 align:start position:0% as which will eliminate some of these 00:03:52.599 --> 00:03:54.869 align:start position:0% as which will eliminate some of these details<00:03:53.599> so<00:03:54.040> if<00:03:54.120> we<00:03:54.280> look<00:03:54.480> what<00:03:54.599> we've<00:03:54.760> got 00:03:54.869 --> 00:03:54.879 align:start position:0% details so if we look what we've got 00:03:54.879 --> 00:03:57.429 align:start position:0% details so if we look what we've got here<00:03:55.000> it's<00:03:55.120> a<00:03:55.239> simple<00:03:55.560> variable<00:03:56.439> declaration 00:03:57.429 --> 00:03:57.439 align:start position:0% here it's a simple variable declaration 00:03:57.439 --> 00:03:59.750 align:start position:0% here it's a simple variable declaration now<00:03:57.640> it<00:03:57.799> consists<00:03:58.280> of<00:03:58.560> a<00:03:58.799> type<00:03:59.079> name<00:03:59.519> which 00:03:59.750 --> 00:03:59.760 align:start position:0% now it consists of a type name which 00:03:59.760 --> 00:04:02.190 align:start position:0% now it consists of a type name which which<00:03:59.840> is<00:03:59.959> uint<00:04:00.840> then<00:04:01.000> some<00:04:01.239> wh<00:04:01.560> space<00:04:01.959> an 00:04:02.190 --> 00:04:02.200 align:start position:0% which is uint then some wh space an 00:04:02.200 --> 00:04:05.069 align:start position:0% which is uint then some wh space an identifier<00:04:02.959> some<00:04:03.200> wh<00:04:03.560> space<00:04:04.360> punctuation 00:04:05.069 --> 00:04:05.079 align:start position:0% identifier some wh space punctuation 00:04:05.079 --> 00:04:07.550 align:start position:0% identifier some wh space punctuation your<00:04:05.239> equal<00:04:05.680> sign<00:04:06.319> some<00:04:06.560> Whit<00:04:06.840> space<00:04:07.120> a<00:04:07.280> number 00:04:07.550 --> 00:04:07.560 align:start position:0% your equal sign some Whit space a number 00:04:07.560 --> 00:04:11.149 align:start position:0% your equal sign some Whit space a number literal<00:04:08.120> one<00:04:08.840> and<00:04:08.959> then<00:04:09.120> the 00:04:11.149 --> 00:04:11.159 align:start position:0% literal one and then the 00:04:11.159 --> 00:04:13.990 align:start position:0% literal one and then the semicolon<00:04:12.159> now<00:04:12.959> what's<00:04:13.200> crucial<00:04:13.519> to 00:04:13.990 --> 00:04:14.000 align:start position:0% semicolon now what's crucial to 00:04:14.000 --> 00:04:17.150 align:start position:0% semicolon now what's crucial to understand<00:04:14.799> is<00:04:15.040> that<00:04:15.560> we're<00:04:16.560> preserving 00:04:17.150 --> 00:04:17.160 align:start position:0% understand is that we're preserving 00:04:17.160 --> 00:04:18.949 align:start position:0% understand is that we're preserving every<00:04:17.400> single<00:04:17.799> character<00:04:18.239> in<00:04:18.400> fact<00:04:18.600> even<00:04:18.799> if 00:04:18.949 --> 00:04:18.959 align:start position:0% every single character in fact even if 00:04:18.959 --> 00:04:20.949 align:start position:0% every single character in fact even if there's<00:04:19.120> an<00:04:19.320> error<00:04:19.680> in<00:04:19.799> the<00:04:19.919> source<00:04:20.320> code 00:04:20.949 --> 00:04:20.959 align:start position:0% there's an error in the source code 00:04:20.959 --> 00:04:22.710 align:start position:0% there's an error in the source code you'll<00:04:21.199> find<00:04:21.440> it<00:04:21.600> in<00:04:21.680> the<00:04:21.840> concrete<00:04:22.280> syntax 00:04:22.710 --> 00:04:22.720 align:start position:0% you'll find it in the concrete syntax 00:04:22.720 --> 00:04:25.430 align:start position:0% you'll find it in the concrete syntax tree<00:04:23.000> so<00:04:23.199> why<00:04:23.320> is<00:04:23.479> this<00:04:24.080> important<00:04:25.080> well<00:04:25.280> when 00:04:25.430 --> 00:04:25.440 align:start position:0% tree so why is this important well when 00:04:25.440 --> 00:04:28.469 align:start position:0% tree so why is this important well when we're<00:04:26.040> developing<00:04:27.040> uh<00:04:27.479> building<00:04:27.919> developer 00:04:28.469 --> 00:04:28.479 align:start position:0% we're developing uh building developer 00:04:28.479 --> 00:04:31.469 align:start position:0% we're developing uh building developer tools<00:04:29.479> uh<00:04:29.720> or<00:04:29.919> transforming<00:04:30.680> code<00:04:31.000> we<00:04:31.199> often 00:04:31.469 --> 00:04:31.479 align:start position:0% tools uh or transforming code we often 00:04:31.479 --> 00:04:33.430 align:start position:0% tools uh or transforming code we often need<00:04:31.759> the<00:04:31.960> complete<00:04:32.400> information<00:04:32.960> so<00:04:33.160> we<00:04:33.280> can 00:04:33.430 --> 00:04:33.440 align:start position:0% need the complete information so we can 00:04:33.440 --> 00:04:35.749 align:start position:0% need the complete information so we can round<00:04:33.840> trip<00:04:34.720> if<00:04:34.840> we<00:04:34.960> were<00:04:35.160> just<00:04:35.360> concerned 00:04:35.749 --> 00:04:35.759 align:start position:0% round trip if we were just concerned 00:04:35.759 --> 00:04:37.070 align:start position:0% round trip if we were just concerned with<00:04:35.880> the<00:04:36.000> meaning<00:04:36.240> of<00:04:36.360> the<00:04:36.520> code<00:04:36.759> then<00:04:36.880> we'd 00:04:37.070 --> 00:04:37.080 align:start position:0% with the meaning of the code then we'd 00:04:37.080 --> 00:04:39.749 align:start position:0% with the meaning of the code then we'd use<00:04:37.240> an<00:04:37.360> abstract<00:04:37.840> syntax<00:04:38.280> tree<00:04:39.120> but<00:04:39.280> for<00:04:39.479> many 00:04:39.749 --> 00:04:39.759 align:start position:0% use an abstract syntax tree but for many 00:04:39.759 --> 00:04:42.189 align:start position:0% use an abstract syntax tree but for many tools<00:04:40.600> like<00:04:40.840> formatters<00:04:41.600> linters<00:04:42.039> or 00:04:42.189 --> 00:04:42.199 align:start position:0% tools like formatters linters or 00:04:42.199 --> 00:04:44.350 align:start position:0% tools like formatters linters or refactoring<00:04:42.759> tools<00:04:43.479> we<00:04:43.639> often<00:04:43.840> want<00:04:44.039> the<00:04:44.120> full 00:04:44.350 --> 00:04:44.360 align:start position:0% refactoring tools we often want the full 00:04:44.360 --> 00:04:45.909 align:start position:0% refactoring tools we often want the full syntactic<00:04:44.880> details<00:04:45.280> you<00:04:45.360> don't<00:04:45.479> want<00:04:45.560> to<00:04:45.680> lose 00:04:45.909 --> 00:04:45.919 align:start position:0% syntactic details you don't want to lose 00:04:45.919 --> 00:04:47.070 align:start position:0% syntactic details you don't want to lose comments<00:04:46.280> when<00:04:46.400> you're 00:04:47.070 --> 00:04:47.080 align:start position:0% comments when you're 00:04:47.080 --> 00:04:49.150 align:start position:0% comments when you're refactoring<00:04:48.080> uh<00:04:48.240> and<00:04:48.639> sometimes<00:04:48.840> you<00:04:48.919> want<00:04:49.039> to 00:04:49.150 --> 00:04:49.160 align:start position:0% refactoring uh and sometimes you want to 00:04:49.160 --> 00:04:51.990 align:start position:0% refactoring uh and sometimes you want to know<00:04:49.440> if<00:04:49.520> you've<00:04:49.720> left<00:04:49.960> two<00:04:50.240> blank<00:04:50.880> lines<00:04:51.880> uh 00:04:51.990 --> 00:04:52.000 align:start position:0% know if you've left two blank lines uh 00:04:52.000 --> 00:04:53.629 align:start position:0% know if you've left two blank lines uh and<00:04:52.080> you<00:04:52.160> want<00:04:52.280> to<00:04:52.440> preserve 00:04:53.629 --> 00:04:53.639 align:start position:0% and you want to preserve 00:04:53.639 --> 00:04:57.029 align:start position:0% and you want to preserve that<00:04:54.639> this<00:04:54.960> level<00:04:55.199> of<00:04:55.400> detail<00:04:56.000> is<00:04:56.240> great<00:04:56.919> but 00:04:57.029 --> 00:04:57.039 align:start position:0% that this level of detail is great but 00:04:57.039 --> 00:04:58.909 align:start position:0% that this level of detail is great but it's<00:04:57.240> also<00:04:57.520> challenging<00:04:58.000> it's<00:04:58.320> quite 00:04:58.909 --> 00:04:58.919 align:start position:0% it's also challenging it's quite 00:04:58.919 --> 00:05:01.469 align:start position:0% it's also challenging it's quite difficult<00:04:59.199> to<00:04:59.840> process<00:05:00.360> this<00:05:01.080> on<00:05:01.199> the<00:05:01.320> one 00:05:01.469 --> 00:05:01.479 align:start position:0% difficult to process this on the one 00:05:01.479 --> 00:05:03.590 align:start position:0% difficult to process this on the one hand<00:05:01.680> we<00:05:01.800> have<00:05:01.960> complete<00:05:02.440> information<00:05:03.440> but 00:05:03.590 --> 00:05:03.600 align:start position:0% hand we have complete information but 00:05:03.600 --> 00:05:05.270 align:start position:0% hand we have complete information but working<00:05:03.919> with<00:05:04.120> detailed<00:05:04.600> trees<00:05:04.919> can<00:05:05.080> be 00:05:05.270 --> 00:05:05.280 align:start position:0% working with detailed trees can be 00:05:05.280 --> 00:05:06.629 align:start position:0% working with detailed trees can be complex<00:05:05.680> and<00:05:05.840> that's<00:05:06.000> the<00:05:06.120> challenge<00:05:06.479> that 00:05:06.629 --> 00:05:06.639 align:start position:0% complex and that's the challenge that 00:05:06.639 --> 00:05:10.189 align:start position:0% complex and that's the challenge that the<00:05:06.759> query<00:05:07.120> API<00:05:08.120> solves<00:05:09.120> so<00:05:09.320> from<00:05:09.520> now<00:05:09.720> on<00:05:10.000> I'll 00:05:10.189 --> 00:05:10.199 align:start position:0% the query API solves so from now on I'll 00:05:10.199 --> 00:05:12.670 align:start position:0% the query API solves so from now on I'll admit<00:05:10.520> trivia<00:05:10.919> nodes<00:05:11.240> and<00:05:11.440> white<00:05:11.759> space<00:05:12.520> from 00:05:12.670 --> 00:05:12.680 align:start position:0% admit trivia nodes and white space from 00:05:12.680 --> 00:05:15.550 align:start position:0% admit trivia nodes and white space from the<00:05:12.960> examples<00:05:13.960> they're<00:05:14.160> still<00:05:14.479> there<00:05:14.759> but<00:05:15.400> you 00:05:15.550 --> 00:05:15.560 align:start position:0% the examples they're still there but you 00:05:15.560 --> 00:05:19.350 align:start position:0% the examples they're still there but you I<00:05:15.680> don't<00:05:15.840> need<00:05:16.000> to<00:05:16.080> show<00:05:16.680> them<00:05:18.039> so<00:05:19.039> let's<00:05:19.240> look 00:05:19.350 --> 00:05:19.360 align:start position:0% I don't need to show them so let's look 00:05:19.360 --> 00:05:22.590 align:start position:0% I don't need to show them so let's look at<00:05:19.479> a<00:05:19.600> slightly<00:05:20.039> more<00:05:20.639> complex<00:05:21.400> example<00:05:22.400> this 00:05:22.590 --> 00:05:22.600 align:start position:0% at a slightly more complex example this 00:05:22.600 --> 00:05:24.790 align:start position:0% at a slightly more complex example this definition<00:05:23.280> shows<00:05:23.880> how<00:05:24.160> different<00:05:24.400> elements 00:05:24.790 --> 00:05:24.800 align:start position:0% definition shows how different elements 00:05:24.800 --> 00:05:26.070 align:start position:0% definition shows how different elements Nest<00:05:25.080> within<00:05:25.400> each 00:05:26.070 --> 00:05:26.080 align:start position:0% Nest within each 00:05:26.080 --> 00:05:28.510 align:start position:0% Nest within each other<00:05:27.080> uh<00:05:27.280> and<00:05:27.479> once<00:05:27.720> again<00:05:27.919> notice<00:05:28.280> how 00:05:28.510 --> 00:05:28.520 align:start position:0% other uh and once again notice how 00:05:28.520 --> 00:05:31.150 align:start position:0% other uh and once again notice how everything<00:05:28.880> is<00:05:29.160> preserved<00:05:29.840> here<00:05:30.560> we've<00:05:30.759> got<00:05:30.960> a 00:05:31.150 --> 00:05:31.160 align:start position:0% everything is preserved here we've got a 00:05:31.160 --> 00:05:32.990 align:start position:0% everything is preserved here we've got a function<00:05:31.639> definition<00:05:32.199> we've<00:05:32.360> got<00:05:32.600> the<00:05:32.840> the 00:05:32.990 --> 00:05:33.000 align:start position:0% function definition we've got the the 00:05:33.000 --> 00:05:35.309 align:start position:0% function definition we've got the the keyword<00:05:33.560> function<00:05:34.080> the<00:05:34.199> identifier<00:05:35.120> we've 00:05:35.309 --> 00:05:35.319 align:start position:0% keyword function the identifier we've 00:05:35.319 --> 00:05:36.749 align:start position:0% keyword function the identifier we've got<00:05:35.400> a<00:05:35.520> parameter<00:05:35.919> list<00:05:36.199> which<00:05:36.319> in<00:05:36.440> this<00:05:36.600> case 00:05:36.749 --> 00:05:36.759 align:start position:0% got a parameter list which in this case 00:05:36.759 --> 00:05:39.029 align:start position:0% got a parameter list which in this case is<00:05:36.919> empty<00:05:37.240> but<00:05:37.360> we<00:05:37.520> still<00:05:38.120> preserve<00:05:38.479> it<00:05:38.919> and 00:05:39.029 --> 00:05:39.039 align:start position:0% is empty but we still preserve it and 00:05:39.039 --> 00:05:40.710 align:start position:0% is empty but we still preserve it and then<00:05:39.199> nested<00:05:39.600> in<00:05:39.720> that<00:05:39.880> is<00:05:40.000> a<00:05:40.120> block<00:05:40.360> and<00:05:40.479> a 00:05:40.710 --> 00:05:40.720 align:start position:0% then nested in that is a block and a 00:05:40.720 --> 00:05:43.990 align:start position:0% then nested in that is a block and a return<00:05:41.000> statement<00:05:42.000> and<00:05:42.160> so 00:05:43.990 --> 00:05:44.000 align:start position:0% return statement and so 00:05:44.000 --> 00:05:48.189 align:start position:0% return statement and so on<00:05:45.000> now<00:05:45.280> this<00:05:45.400> level<00:05:45.680> of<00:05:45.840> detail<00:05:46.520> allows<00:05:46.919> us<00:05:47.240> to 00:05:48.189 --> 00:05:48.199 align:start position:0% on now this level of detail allows us to 00:05:48.199 --> 00:05:50.469 align:start position:0% on now this level of detail allows us to maintain<00:05:49.080> complete<00:05:49.400> Source<00:05:49.720> Fidelity<00:05:50.240> as<00:05:50.360> I 00:05:50.469 --> 00:05:50.479 align:start position:0% maintain complete Source Fidelity as I 00:05:50.479 --> 00:05:52.469 align:start position:0% maintain complete Source Fidelity as I said<00:05:50.639> if<00:05:50.720> we're<00:05:50.880> going<00:05:51.000> to<00:05:51.199> roundtrip<00:05:52.199> we<00:05:52.319> can 00:05:52.469 --> 00:05:52.479 align:start position:0% said if we're going to roundtrip we can 00:05:52.479 --> 00:05:55.350 align:start position:0% said if we're going to roundtrip we can track<00:05:52.800> precise<00:05:53.240> cord<00:05:53.800> code<00:05:54.080> locations<00:05:55.080> so<00:05:55.280> if 00:05:55.350 --> 00:05:55.360 align:start position:0% track precise cord code locations so if 00:05:55.360 --> 00:05:57.350 align:start position:0% track precise cord code locations so if you<00:05:55.479> want<00:05:55.600> to<00:05:55.720> do<00:05:56.039> error 00:05:57.350 --> 00:05:57.360 align:start position:0% you want to do error 00:05:57.360 --> 00:06:01.270 align:start position:0% you want to do error reporting<00:05:58.360> uh<00:05:58.759> it<00:05:59.199> handles<00:05:59.720> formatting 00:06:01.270 --> 00:06:01.280 align:start position:0% reporting uh it handles formatting 00:06:01.280 --> 00:06:04.430 align:start position:0% reporting uh it handles formatting preservation<00:06:02.720> and<00:06:03.720> when<00:06:03.919> you're<00:06:04.120> Building 00:06:04.430 --> 00:06:04.440 align:start position:0% preservation and when you're Building 00:06:04.440 --> 00:06:06.150 align:start position:0% preservation and when you're Building Development<00:06:04.800> tools<00:06:05.160> this<00:06:05.319> detailed 00:06:06.150 --> 00:06:06.160 align:start position:0% Development tools this detailed 00:06:06.160 --> 00:06:08.150 align:start position:0% Development tools this detailed structure<00:06:06.960> is 00:06:08.150 --> 00:06:08.160 align:start position:0% structure is 00:06:08.160 --> 00:06:10.189 align:start position:0% structure is essential<00:06:09.160> for<00:06:09.479> certain<00:06:09.800> class<00:06:10.039> of 00:06:10.189 --> 00:06:10.199 align:start position:0% essential for certain class of 00:06:10.199 --> 00:06:11.990 align:start position:0% essential for certain class of development 00:06:11.990 --> 00:06:12.000 align:start position:0% development 00:06:12.000 --> 00:06:15.350 align:start position:0% development tools<00:06:13.000> so<00:06:13.360> to<00:06:13.560> emphasize<00:06:14.039> this<00:06:14.240> point<00:06:15.120> and<00:06:15.240> I 00:06:15.350 --> 00:06:15.360 align:start position:0% tools so to emphasize this point and I 00:06:15.360 --> 00:06:17.230 align:start position:0% tools so to emphasize this point and I know<00:06:15.720> I'm<00:06:15.880> being<00:06:16.280> repetitive<00:06:16.800> here<00:06:16.960> I<00:06:17.080> really 00:06:17.230 --> 00:06:17.240 align:start position:0% know I'm being repetitive here I really 00:06:17.240 --> 00:06:19.150 align:start position:0% know I'm being repetitive here I really want<00:06:17.319> to<00:06:17.479> make<00:06:17.680> this<00:06:17.880> point<00:06:18.199> though<00:06:18.840> why<00:06:18.960> do<00:06:19.039> we 00:06:19.150 --> 00:06:19.160 align:start position:0% want to make this point though why do we 00:06:19.160 --> 00:06:22.870 align:start position:0% want to make this point though why do we need<00:06:19.280> a<00:06:19.440> concrete<00:06:19.840> syntax<00:06:20.560> tree<00:06:21.560> well<00:06:22.319> we 00:06:22.870 --> 00:06:22.880 align:start position:0% need a concrete syntax tree well we 00:06:22.880 --> 00:06:25.790 align:start position:0% need a concrete syntax tree well we really<00:06:23.240> want<00:06:23.520> to<00:06:24.039> in<00:06:24.199> a<00:06:24.360> lot<00:06:24.560> of<00:06:24.720> tools<00:06:25.599> for 00:06:25.790 --> 00:06:25.800 align:start position:0% really want to in a lot of tools for 00:06:25.800 --> 00:06:29.589 align:start position:0% really want to in a lot of tools for example<00:06:26.120> in<00:06:26.720> pra<00:06:27.720> uh<00:06:27.919> which<00:06:28.639> is<00:06:28.880> now<00:06:29.240> used 00:06:29.589 --> 00:06:29.599 align:start position:0% example in pra uh which is now used 00:06:29.599 --> 00:06:31.790 align:start position:0% example in pra uh which is now used using<00:06:29.919> slang<00:06:30.440> by<00:06:30.560> the<00:06:30.680> way<00:06:31.080> using<00:06:31.440> this 00:06:31.790 --> 00:06:31.800 align:start position:0% using slang by the way using this 00:06:31.800 --> 00:06:34.830 align:start position:0% using slang by the way using this technology<00:06:32.800> uh<00:06:32.960> pretty<00:06:33.199> a<00:06:33.560> solidity<00:06:34.560> we<00:06:34.720> want 00:06:34.830 --> 00:06:34.840 align:start position:0% technology uh pretty a solidity we want 00:06:34.840 --> 00:06:36.670 align:start position:0% technology uh pretty a solidity we want to<00:06:35.000> make<00:06:35.199> sure<00:06:35.479> that<00:06:35.639> we<00:06:35.759> can<00:06:35.919> preserve<00:06:36.440> every 00:06:36.670 --> 00:06:36.680 align:start position:0% to make sure that we can preserve every 00:06:36.680 --> 00:06:39.270 align:start position:0% to make sure that we can preserve every single<00:06:37.120> character<00:06:37.840> especially<00:06:38.319> comments<00:06:39.080> for 00:06:39.270 --> 00:06:39.280 align:start position:0% single character especially comments for 00:06:39.280 --> 00:06:40.790 align:start position:0% single character especially comments for example<00:06:39.680> you<00:06:39.800> might<00:06:40.000> have<00:06:40.120> a<00:06:40.240> tool<00:06:40.479> that<00:06:40.599> wants 00:06:40.790 --> 00:06:40.800 align:start position:0% example you might have a tool that wants 00:06:40.800 --> 00:06:43.390 align:start position:0% example you might have a tool that wants to<00:06:40.919> deal<00:06:41.199> with<00:06:41.400> comments<00:06:42.280> wants<00:06:42.520> to<00:06:42.840> encode 00:06:43.390 --> 00:06:43.400 align:start position:0% to deal with comments wants to encode 00:06:43.400 --> 00:06:45.070 align:start position:0% to deal with comments wants to encode validation<00:06:44.000> information<00:06:44.479> in<00:06:44.599> a<00:06:44.800> special 00:06:45.070 --> 00:06:45.080 align:start position:0% validation information in a special 00:06:45.080 --> 00:06:46.870 align:start position:0% validation information in a special comment<00:06:45.360> format<00:06:46.319> not<00:06:46.520> like<00:06:46.720> the 00:06:46.870 --> 00:06:46.880 align:start position:0% comment format not like the 00:06:46.880 --> 00:06:49.070 align:start position:0% comment format not like the documentation<00:06:47.639> comment<00:06:48.520> but<00:06:48.680> your<00:06:48.840> own 00:06:49.070 --> 00:06:49.080 align:start position:0% documentation comment but your own 00:06:49.080 --> 00:06:50.550 align:start position:0% documentation comment but your own special<00:06:49.400> comment<00:06:49.720> format<00:06:50.080> so<00:06:50.199> you<00:06:50.280> want<00:06:50.400> to 00:06:50.550 --> 00:06:50.560 align:start position:0% special comment format so you want to 00:06:50.560 --> 00:06:52.830 align:start position:0% special comment format so you want to preserve<00:06:50.960> those 00:06:52.830 --> 00:06:52.840 align:start position:0% preserve those 00:06:52.840 --> 00:06:56.790 align:start position:0% preserve those comments<00:06:53.840> an<00:06:54.039> as<00:06:54.800> on<00:06:54.919> the<00:06:55.039> other<00:06:55.280> hand<00:06:56.280> is 00:06:56.790 --> 00:06:56.800 align:start position:0% comments an as on the other hand is 00:06:56.800 --> 00:06:58.390 align:start position:0% comments an as on the other hand is focusing<00:06:57.199> on<00:06:57.360> the<00:06:57.520> essential<00:06:57.960> structure 00:06:58.390 --> 00:06:58.400 align:start position:0% focusing on the essential structure 00:06:58.400 --> 00:07:00.790 align:start position:0% focusing on the essential structure which<00:06:58.520> is<00:06:58.680> good<00:06:58.840> for<00:06:59.080> seman<00:06:59.840> processing 00:07:00.790 --> 00:07:00.800 align:start position:0% which is good for seman processing 00:07:00.800 --> 00:07:02.110 align:start position:0% which is good for seman processing doesn't<00:07:01.160> contain<00:07:01.479> the<00:07:01.599> formatting 00:07:02.110 --> 00:07:02.120 align:start position:0% doesn't contain the formatting 00:07:02.120 --> 00:07:04.390 align:start position:0% doesn't contain the formatting information<00:07:03.120> simplifies 00:07:04.390 --> 00:07:04.400 align:start position:0% information simplifies 00:07:04.400 --> 00:07:06.790 align:start position:0% information simplifies expressions<00:07:05.400> and<00:07:05.639> it<00:07:05.800> adits<00:07:06.080> all<00:07:06.319> comments<00:07:06.639> in 00:07:06.790 --> 00:07:06.800 align:start position:0% expressions and it adits all comments in 00:07:06.800 --> 00:07:12.670 align:start position:0% expressions and it adits all comments in white 00:07:12.670 --> 00:07:12.680 align:start position:0% 00:07:12.680 --> 00:07:15.070 align:start position:0% space<00:07:13.680> so<00:07:13.960> now<00:07:14.120> that<00:07:14.240> we<00:07:14.639> understand<00:07:14.840> what<00:07:14.919> a 00:07:15.070 --> 00:07:15.080 align:start position:0% space so now that we understand what a 00:07:15.080 --> 00:07:17.749 align:start position:0% space so now that we understand what a CST<00:07:15.520> is<00:07:15.680> for<00:07:16.400> let's<00:07:16.840> look<00:07:17.000> at<00:07:17.160> how<00:07:17.360> you<00:07:17.520> might 00:07:17.749 --> 00:07:17.759 align:start position:0% CST is for let's look at how you might 00:07:17.759 --> 00:07:20.909 align:start position:0% CST is for let's look at how you might traditionally<00:07:18.479> process<00:07:18.840> a<00:07:19.400> CST<00:07:20.400> so<00:07:20.680> this<00:07:20.759> is 00:07:20.909 --> 00:07:20.919 align:start position:0% traditionally process a CST so this is 00:07:20.919 --> 00:07:23.710 align:start position:0% traditionally process a CST so this is the<00:07:21.120> kind<00:07:21.280> of<00:07:21.479> code<00:07:21.800> that<00:07:21.960> you<00:07:22.360> often<00:07:22.639> see<00:07:23.560> a 00:07:23.710 --> 00:07:23.720 align:start position:0% the kind of code that you often see a 00:07:23.720 --> 00:07:25.950 align:start position:0% the kind of code that you often see a lot<00:07:24.000> of<00:07:25.000> you<00:07:25.160> know<00:07:25.319> what<00:07:25.440> it's<00:07:25.639> like<00:07:25.800> to 00:07:25.950 --> 00:07:25.960 align:start position:0% lot of you know what it's like to 00:07:25.960 --> 00:07:28.390 align:start position:0% lot of you know what it's like to Traverse<00:07:26.360> a<00:07:26.520> tree<00:07:27.000> especially<00:07:27.400> a<00:07:27.560> very<00:07:27.840> deep 00:07:28.390 --> 00:07:28.400 align:start position:0% Traverse a tree especially a very deep 00:07:28.400 --> 00:07:29.990 align:start position:0% Traverse a tree especially a very deep and<00:07:28.639> complex<00:07:29.080> tree<00:07:29.319> which<00:07:29.520> which<00:07:29.599> is<00:07:29.759> what<00:07:29.840> you 00:07:29.990 --> 00:07:30.000 align:start position:0% and complex tree which which is what you 00:07:30.000 --> 00:07:31.869 align:start position:0% and complex tree which which is what you typically<00:07:30.360> get<00:07:30.560> out<00:07:30.680> of<00:07:30.800> a 00:07:31.869 --> 00:07:31.879 align:start position:0% typically get out of a 00:07:31.879 --> 00:07:35.230 align:start position:0% typically get out of a compiler<00:07:32.879> uh<00:07:33.160> and<00:07:33.280> it's<00:07:33.440> not<00:07:34.120> pretty<00:07:35.120> what 00:07:35.230 --> 00:07:35.240 align:start position:0% compiler uh and it's not pretty what 00:07:35.240 --> 00:07:36.670 align:start position:0% compiler uh and it's not pretty what we're<00:07:35.400> trying<00:07:35.599> to<00:07:35.759> do<00:07:36.000> is<00:07:36.199> actually<00:07:36.479> quite 00:07:36.670 --> 00:07:36.680 align:start position:0% we're trying to do is actually quite 00:07:36.680 --> 00:07:37.990 align:start position:0% we're trying to do is actually quite simple<00:07:37.000> we<00:07:37.120> just<00:07:37.199> want<00:07:37.360> to<00:07:37.520> find<00:07:37.720> all<00:07:37.879> the 00:07:37.990 --> 00:07:38.000 align:start position:0% simple we just want to find all the 00:07:38.000 --> 00:07:40.510 align:start position:0% simple we just want to find all the variable<00:07:38.520> declarations<00:07:39.520> in<00:07:39.720> some<00:07:39.919> solidity 00:07:40.510 --> 00:07:40.520 align:start position:0% variable declarations in some solidity 00:07:40.520 --> 00:07:43.070 align:start position:0% variable declarations in some solidity code<00:07:41.360> but<00:07:41.560> look<00:07:41.720> at<00:07:41.919> what<00:07:42.039> we<00:07:42.199> have<00:07:42.319> to 00:07:43.070 --> 00:07:43.080 align:start position:0% code but look at what we have to 00:07:43.080 --> 00:07:45.469 align:start position:0% code but look at what we have to do<00:07:44.080> so<00:07:44.440> first<00:07:44.639> of<00:07:44.800> all<00:07:44.960> we're<00:07:45.080> writing<00:07:45.319> a 00:07:45.469 --> 00:07:45.479 align:start position:0% do so first of all we're writing a 00:07:45.479 --> 00:07:47.430 align:start position:0% do so first of all we're writing a recursive<00:07:46.000> function<00:07:46.599> we<00:07:46.720> need<00:07:46.919> recursion 00:07:47.430 --> 00:07:47.440 align:start position:0% recursive function we need recursion 00:07:47.440 --> 00:07:48.629 align:start position:0% recursive function we need recursion because<00:07:47.599> we<00:07:47.720> don't<00:07:47.879> know<00:07:48.039> how<00:07:48.199> deep<00:07:48.360> in<00:07:48.479> the 00:07:48.629 --> 00:07:48.639 align:start position:0% because we don't know how deep in the 00:07:48.639 --> 00:07:51.510 align:start position:0% because we don't know how deep in the tree<00:07:49.240> it<00:07:49.400> is<00:07:50.360> could<00:07:50.520> be<00:07:50.639> at<00:07:50.759> the<00:07:50.879> contract 00:07:51.510 --> 00:07:51.520 align:start position:0% tree it is could be at the contract 00:07:51.520 --> 00:07:54.270 align:start position:0% tree it is could be at the contract inside<00:07:51.800> a<00:07:51.960> function<00:07:52.479> inside<00:07:52.759> a<00:07:52.879> block 00:07:54.270 --> 00:07:54.280 align:start position:0% inside a function inside a block 00:07:54.280 --> 00:07:57.869 align:start position:0% inside a function inside a block anywhere<00:07:55.280> and<00:07:55.479> then<00:07:55.879> when<00:07:56.039> we<00:07:56.199> find<00:07:56.479> each<00:07:56.879> node 00:07:57.869 --> 00:07:57.879 align:start position:0% anywhere and then when we find each node 00:07:57.879 --> 00:08:00.469 align:start position:0% anywhere and then when we find each node we've<00:07:58.159> got<00:07:58.319> to<00:07:58.560> manually<00:07:58.960> check<00:07:59.159> its<00:07:59.599> kind 00:08:00.469 --> 00:08:00.479 align:start position:0% we've got to manually check its kind 00:08:00.479 --> 00:08:03.230 align:start position:0% we've got to manually check its kind we've<00:08:00.720> got<00:08:00.919> to<00:08:01.319> search<00:08:01.759> through<00:08:02.159> the<00:08:03.039> uh 00:08:03.230 --> 00:08:03.240 align:start position:0% we've got to search through the uh 00:08:03.240 --> 00:08:05.189 align:start position:0% we've got to search through the uh children<00:08:04.120> we've<00:08:04.280> got<00:08:04.400> to<00:08:04.560> handle<00:08:04.879> all<00:08:05.039> the 00:08:05.189 --> 00:08:05.199 align:start position:0% children we've got to handle all the 00:08:05.199 --> 00:08:07.070 align:start position:0% children we've got to handle all the edge<00:08:05.599> cases<00:08:06.120> and<00:08:06.280> we've<00:08:06.440> got<00:08:06.520> to<00:08:06.639> manage<00:08:06.960> the 00:08:07.070 --> 00:08:07.080 align:start position:0% edge cases and we've got to manage the 00:08:07.080 --> 00:08:09.029 align:start position:0% edge cases and we've got to manage the recursion<00:08:07.680> stack<00:08:08.520> especially<00:08:08.840> if<00:08:08.919> you're 00:08:09.029 --> 00:08:09.039 align:start position:0% recursion stack especially if you're 00:08:09.039 --> 00:08:11.670 align:start position:0% recursion stack especially if you're threading<00:08:09.520> State<00:08:10.360> and<00:08:10.479> this<00:08:10.599> is<00:08:10.720> a<00:08:10.919> simple 00:08:11.670 --> 00:08:11.680 align:start position:0% threading State and this is a simple 00:08:11.680 --> 00:08:14.070 align:start position:0% threading State and this is a simple example<00:08:12.680> in<00:08:12.879> real<00:08:13.199> life<00:08:13.400> code<00:08:13.680> you'd<00:08:13.879> have<00:08:14.000> to 00:08:14.070 --> 00:08:14.080 align:start position:0% example in real life code you'd have to 00:08:14.080 --> 00:08:16.149 align:start position:0% example in real life code you'd have to handle<00:08:14.319> Eric<00:08:14.720> cases<00:08:15.120> deal<00:08:15.360> with<00:08:15.560> unexpected 00:08:16.149 --> 00:08:16.159 align:start position:0% handle Eric cases deal with unexpected 00:08:16.159 --> 00:08:18.189 align:start position:0% handle Eric cases deal with unexpected node<00:08:16.520> types<00:08:17.240> which<00:08:17.360> is<00:08:17.520> what<00:08:17.639> you<00:08:17.759> can<00:08:17.919> get<00:08:18.120> if 00:08:18.189 --> 00:08:18.199 align:start position:0% node types which is what you can get if 00:08:18.199 --> 00:08:19.790 align:start position:0% node types which is what you can get if you've<00:08:18.360> got<00:08:18.479> a<00:08:18.599> source<00:08:18.919> code<00:08:19.159> error<00:08:19.520> for 00:08:19.790 --> 00:08:19.800 align:start position:0% you've got a source code error for 00:08:19.800 --> 00:08:21.990 align:start position:0% you've got a source code error for example<00:08:20.800> manage<00:08:21.159> your<00:08:21.360> state<00:08:21.680> during 00:08:21.990 --> 00:08:22.000 align:start position:0% example manage your state during 00:08:22.000 --> 00:08:23.350 align:start position:0% example manage your state during traversal<00:08:22.639> and<00:08:22.759> if<00:08:22.840> you've<00:08:23.000> written<00:08:23.240> a 00:08:23.350 --> 00:08:23.360 align:start position:0% traversal and if you've written a 00:08:23.360 --> 00:08:24.990 align:start position:0% traversal and if you've written a visitor<00:08:23.800> patent<00:08:24.120> you<00:08:24.240> know<00:08:24.400> that<00:08:24.520> it's<00:08:24.639> a<00:08:24.800> pain 00:08:24.990 --> 00:08:25.000 align:start position:0% visitor patent you know that it's a pain 00:08:25.000 --> 00:08:27.149 align:start position:0% visitor patent you know that it's a pain in<00:08:25.120> the<00:08:25.240> ask<00:08:25.479> to<00:08:26.000> manage<00:08:26.360> your 00:08:27.149 --> 00:08:27.159 align:start position:0% in the ask to manage your 00:08:27.159 --> 00:08:29.149 align:start position:0% in the ask to manage your state<00:08:28.159> you've<00:08:28.319> got<00:08:28.400> to<00:08:28.560> handle<00:08:28.919> parent 00:08:29.149 --> 00:08:29.159 align:start position:0% state you've got to handle parent 00:08:29.159 --> 00:08:30.909 align:start position:0% state you've got to handle parent refence<00:08:29.720> es<00:08:29.960> and<00:08:30.039> you've<00:08:30.199> got<00:08:30.280> to<00:08:30.440> manage<00:08:30.759> the 00:08:30.909 --> 00:08:30.919 align:start position:0% refence es and you've got to manage the 00:08:30.919 --> 00:08:32.990 align:start position:0% refence es and you've got to manage the position<00:08:31.280> in<00:08:31.400> the<00:08:31.560> source 00:08:32.990 --> 00:08:33.000 align:start position:0% position in the source 00:08:33.000 --> 00:08:35.350 align:start position:0% position in the source code<00:08:34.000> now<00:08:34.200> the<00:08:34.320> problems<00:08:34.640> with<00:08:34.800> this<00:08:35.000> approach 00:08:35.350 --> 00:08:35.360 align:start position:0% code now the problems with this approach 00:08:35.360 --> 00:08:38.029 align:start position:0% code now the problems with this approach are<00:08:36.000> numerous<00:08:37.000> first<00:08:37.320> it's<00:08:37.560> incredibly 00:08:38.029 --> 00:08:38.039 align:start position:0% are numerous first it's incredibly 00:08:38.039 --> 00:08:39.990 align:start position:0% are numerous first it's incredibly verbose<00:08:38.880> the<00:08:39.000> amount<00:08:39.200> of<00:08:39.320> code<00:08:39.560> you<00:08:39.640> need<00:08:39.839> to 00:08:39.990 --> 00:08:40.000 align:start position:0% verbose the amount of code you need to 00:08:40.000 --> 00:08:42.709 align:start position:0% verbose the amount of code you need to write<00:08:40.200> to<00:08:40.320> do<00:08:40.479> even<00:08:40.719> simple<00:08:41.159> analysis<00:08:41.719> is 00:08:42.709 --> 00:08:42.719 align:start position:0% write to do even simple analysis is 00:08:42.719 --> 00:08:44.910 align:start position:0% write to do even simple analysis is substantial<00:08:43.719> and<00:08:43.839> the<00:08:43.959> more<00:08:44.159> code<00:08:44.440> you<00:08:44.640> write 00:08:44.910 --> 00:08:44.920 align:start position:0% substantial and the more code you write 00:08:44.920 --> 00:08:46.829 align:start position:0% substantial and the more code you write the<00:08:45.000> more<00:08:45.160> you<00:08:45.279> have<00:08:45.480> to<00:08:45.600> maintain<00:08:46.600> and<00:08:46.760> the 00:08:46.829 --> 00:08:46.839 align:start position:0% the more you have to maintain and the 00:08:46.839 --> 00:08:48.949 align:start position:0% the more you have to maintain and the more<00:08:47.080> places<00:08:47.399> there<00:08:47.519> are<00:08:47.640> for<00:08:47.800> bugs<00:08:48.080> to 00:08:48.949 --> 00:08:48.959 align:start position:0% more places there are for bugs to 00:08:48.959 --> 00:08:52.949 align:start position:0% more places there are for bugs to hide<00:08:49.959> uh<00:08:50.120> second<00:08:50.600> it's<00:08:50.839> Error<00:08:51.600> prone<00:08:52.600> uh<00:08:52.760> not 00:08:52.949 --> 00:08:52.959 align:start position:0% hide uh second it's Error prone uh not 00:08:52.959 --> 00:08:54.430 align:start position:0% hide uh second it's Error prone uh not only<00:08:53.240> because<00:08:53.440> of<00:08:53.560> the<00:08:53.680> volume<00:08:53.920> of<00:08:54.040> the<00:08:54.160> code 00:08:54.430 --> 00:08:54.440 align:start position:0% only because of the volume of the code 00:08:54.440 --> 00:08:55.790 align:start position:0% only because of the volume of the code but<00:08:54.560> also<00:08:54.760> it's<00:08:54.920> quite<00:08:55.120> tricky<00:08:55.399> to<00:08:55.519> write 00:08:55.790 --> 00:08:55.800 align:start position:0% but also it's quite tricky to write 00:08:55.800 --> 00:08:56.710 align:start position:0% but also it's quite tricky to write these<00:08:55.959> when<00:08:56.080> you're<00:08:56.200> dealing<00:08:56.519> with 00:08:56.710 --> 00:08:56.720 align:start position:0% these when you're dealing with 00:08:56.720 --> 00:08:58.870 align:start position:0% these when you're dealing with complicated<00:08:57.279> trees<00:08:58.279> for<00:08:58.440> example<00:08:58.720> in 00:08:58.870 --> 00:08:58.880 align:start position:0% complicated trees for example in 00:08:58.880 --> 00:09:00.630 align:start position:0% complicated trees for example in solidity<00:08:59.440> variable<00:08:59.800> declarations<00:09:00.399> can 00:09:00.630 --> 00:09:00.640 align:start position:0% solidity variable declarations can 00:09:00.640 --> 00:09:03.870 align:start position:0% solidity variable declarations can appear<00:09:01.399> in<00:09:01.560> for<00:09:01.920> loop<00:09:02.600> initializers<00:09:03.600> I<00:09:03.680> don't 00:09:03.870 --> 00:09:03.880 align:start position:0% appear in for loop initializers I don't 00:09:03.880 --> 00:09:05.949 align:start position:0% appear in for loop initializers I don't know<00:09:04.000> if<00:09:04.120> this<00:09:04.279> code<00:09:04.519> would<00:09:04.720> handle 00:09:05.949 --> 00:09:05.959 align:start position:0% know if this code would handle 00:09:05.959 --> 00:09:09.030 align:start position:0% know if this code would handle that<00:09:06.959> it's<00:09:07.120> a<00:09:07.399> question<00:09:07.680> for<00:09:07.839> the<00:09:07.959> reader<00:09:08.880> it's 00:09:09.030 --> 00:09:09.040 align:start position:0% that it's a question for the reader it's 00:09:09.040 --> 00:09:11.430 align:start position:0% that it's a question for the reader it's hard<00:09:09.240> to<00:09:09.720> maintain<00:09:10.720> when<00:09:10.920> the<00:09:11.040> language 00:09:11.430 --> 00:09:11.440 align:start position:0% hard to maintain when the language 00:09:11.440 --> 00:09:14.910 align:start position:0% hard to maintain when the language evolves<00:09:11.880> and<00:09:12.079> as<00:09:12.200> you<00:09:12.320> know<00:09:12.600> solidity<00:09:13.240> evolves 00:09:14.910 --> 00:09:14.920 align:start position:0% evolves and as you know solidity evolves 00:09:14.920 --> 00:09:16.670 align:start position:0% evolves and as you know solidity evolves significantly<00:09:15.920> uh<00:09:16.040> in<00:09:16.160> all<00:09:16.320> sorts<00:09:16.560> of 00:09:16.670 --> 00:09:16.680 align:start position:0% significantly uh in all sorts of 00:09:16.680 --> 00:09:20.110 align:start position:0% significantly uh in all sorts of interesting<00:09:17.120> ways<00:09:17.920> like<00:09:18.120> in<00:09:18.680> one<00:09:18.839> of<00:09:18.959> the<00:09:19.120> 0.5s 00:09:20.110 --> 00:09:20.120 align:start position:0% interesting ways like in one of the 0.5s 00:09:20.120 --> 00:09:21.910 align:start position:0% interesting ways like in one of the 0.5s where<00:09:20.320> the<00:09:20.600> exponentiation<00:09:21.519> operator 00:09:21.910 --> 00:09:21.920 align:start position:0% where the exponentiation operator 00:09:21.920 --> 00:09:23.710 align:start position:0% where the exponentiation operator changed 00:09:23.710 --> 00:09:23.720 align:start position:0% changed 00:09:23.720 --> 00:09:25.710 align:start position:0% changed associativity<00:09:24.720> uh<00:09:24.959> so<00:09:25.120> when<00:09:25.240> the<00:09:25.360> language 00:09:25.710 --> 00:09:25.720 align:start position:0% associativity uh so when the language 00:09:25.720 --> 00:09:26.829 align:start position:0% associativity uh so when the language evolves<00:09:26.079> you<00:09:26.160> need<00:09:26.320> to<00:09:26.440> update<00:09:26.720> your 00:09:26.829 --> 00:09:26.839 align:start position:0% evolves you need to update your 00:09:26.839 --> 00:09:29.470 align:start position:0% evolves you need to update your traversal<00:09:27.440> code<00:09:28.440> and<00:09:28.600> that's<00:09:28.800> because<00:09:29.040> the 00:09:29.470 --> 00:09:29.480 align:start position:0% traversal code and that's because the 00:09:29.480 --> 00:09:31.190 align:start position:0% traversal code and that's because the veral<00:09:29.760> code<00:09:30.000> is<00:09:30.160> mixed<00:09:30.399> with<00:09:30.560> the<00:09:30.680> analysis 00:09:31.190 --> 00:09:31.200 align:start position:0% veral code is mixed with the analysis 00:09:31.200 --> 00:09:33.870 align:start position:0% veral code is mixed with the analysis code<00:09:31.760> so<00:09:31.959> what<00:09:32.079> you<00:09:32.160> want<00:09:32.279> to<00:09:32.480> do<00:09:32.800> for<00:09:33.200> analysis 00:09:33.870 --> 00:09:33.880 align:start position:0% code so what you want to do for analysis 00:09:33.880 --> 00:09:36.829 align:start position:0% code so what you want to do for analysis is<00:09:34.000> mixed<00:09:34.320> in<00:09:34.480> with<00:09:34.640> the<00:09:34.800> mechanics<00:09:35.240> of 00:09:36.829 --> 00:09:36.839 align:start position:0% is mixed in with the mechanics of 00:09:36.839 --> 00:09:39.230 align:start position:0% is mixed in with the mechanics of traversal<00:09:37.839> to<00:09:38.040> make<00:09:38.279> changes<00:09:38.880> you're<00:09:39.040> often 00:09:39.230 --> 00:09:39.240 align:start position:0% traversal to make changes you're often 00:09:39.240 --> 00:09:42.430 align:start position:0% traversal to make changes you're often going<00:09:39.360> to<00:09:39.480> break<00:09:39.920> things<00:09:40.920> finally<00:09:41.560> and<00:09:41.760> more 00:09:42.430 --> 00:09:42.440 align:start position:0% going to break things finally and more 00:09:42.440 --> 00:09:44.750 align:start position:0% going to break things finally and more importantly<00:09:43.440> this<00:09:43.680> forces<00:09:44.079> you<00:09:44.200> to<00:09:44.399> think 00:09:44.750 --> 00:09:44.760 align:start position:0% importantly this forces you to think 00:09:44.760 --> 00:09:48.230 align:start position:0% importantly this forces you to think about<00:09:45.760> what<00:09:46.360> or<00:09:46.680> how<00:09:46.920> you<00:09:47.040> want<00:09:47.200> to<00:09:47.360> do<00:09:47.600> things 00:09:48.230 --> 00:09:48.240 align:start position:0% about what or how you want to do things 00:09:48.240 --> 00:09:50.990 align:start position:0% about what or how you want to do things rather<00:09:48.480> than<00:09:48.720> what<00:09:48.880> you<00:09:49.000> want<00:09:49.120> to<00:09:49.720> do<00:09:50.720> and<00:09:50.880> the 00:09:50.990 --> 00:09:51.000 align:start position:0% rather than what you want to do and the 00:09:51.000 --> 00:09:53.110 align:start position:0% rather than what you want to do and the intent<00:09:51.320> of<00:09:51.480> this<00:09:51.680> code<00:09:52.320> finding<00:09:52.760> variable 00:09:53.110 --> 00:09:53.120 align:start position:0% intent of this code finding variable 00:09:53.120 --> 00:09:55.550 align:start position:0% intent of this code finding variable declarations<00:09:53.760> is<00:09:53.959> buried<00:09:54.360> in<00:09:54.600> here<00:09:55.279> you<00:09:55.399> could 00:09:55.550 --> 00:09:55.560 align:start position:0% declarations is buried in here you could 00:09:55.560 --> 00:09:57.509 align:start position:0% declarations is buried in here you could look<00:09:55.680> at<00:09:55.800> a<00:09:55.920> big<00:09:56.160> tra<00:09:56.519> bit<00:09:56.640> of<00:09:56.760> traversal<00:09:57.279> code 00:09:57.509 --> 00:09:57.519 align:start position:0% look at a big tra bit of traversal code 00:09:57.519 --> 00:09:58.870 align:start position:0% look at a big tra bit of traversal code and<00:09:57.640> you<00:09:57.720> wouldn't<00:09:58.040> know<00:09:58.360> what<00:09:58.480> it<00:09:58.600> was<00:09:58.720> meant 00:09:58.870 --> 00:09:58.880 align:start position:0% and you wouldn't know what it was meant 00:09:58.880 --> 00:10:00.350 align:start position:0% and you wouldn't know what it was meant to<00:09:58.959> be<00:09:59.079> doing 00:10:00.350 --> 00:10:00.360 align:start position:0% to be doing 00:10:00.360 --> 00:10:02.150 align:start position:0% to be doing we<00:10:00.519> need<00:10:00.720> something 00:10:02.150 --> 00:10:02.160 align:start position:0% we need something 00:10:02.160 --> 00:10:04.870 align:start position:0% we need something better<00:10:03.160> so<00:10:03.720> we'll<00:10:03.920> have<00:10:04.040> a<00:10:04.279> look<00:10:04.440> at<00:10:04.600> some 00:10:04.870 --> 00:10:04.880 align:start position:0% better so we'll have a look at some 00:10:04.880 --> 00:10:07.509 align:start position:0% better so we'll have a look at some specific<00:10:05.360> challenges<00:10:06.360> with<00:10:06.519> manual 00:10:07.509 --> 00:10:07.519 align:start position:0% specific challenges with manual 00:10:07.519 --> 00:10:10.389 align:start position:0% specific challenges with manual traversal<00:10:08.519> so<00:10:08.880> recursion<00:10:09.519> management<00:10:10.240> you've 00:10:10.389 --> 00:10:10.399 align:start position:0% traversal so recursion management you've 00:10:10.399 --> 00:10:13.150 align:start position:0% traversal so recursion management you've got<00:10:10.519> to<00:10:10.640> handle<00:10:10.920> deep<00:10:11.200> nesting<00:10:12.160> efficiently 00:10:13.150 --> 00:10:13.160 align:start position:0% got to handle deep nesting efficiently 00:10:13.160 --> 00:10:14.750 align:start position:0% got to handle deep nesting efficiently avoiding<00:10:13.560> stack<00:10:13.920> Overflow<00:10:14.440> you've<00:10:14.560> got<00:10:14.680> to 00:10:14.750 --> 00:10:14.760 align:start position:0% avoiding stack Overflow you've got to 00:10:14.760 --> 00:10:16.269 align:start position:0% avoiding stack Overflow you've got to make<00:10:14.880> sure<00:10:15.040> you<00:10:15.160> don't<00:10:15.399> have<00:10:15.560> any<00:10:15.720> infinite 00:10:16.269 --> 00:10:16.279 align:start position:0% make sure you don't have any infinite 00:10:16.279 --> 00:10:18.389 align:start position:0% make sure you don't have any infinite Loops<00:10:17.279> you've<00:10:17.480> got<00:10:17.560> to<00:10:17.720> maintain<00:10:18.160> your 00:10:18.389 --> 00:10:18.399 align:start position:0% Loops you've got to maintain your 00:10:18.399 --> 00:10:20.389 align:start position:0% Loops you've got to maintain your context<00:10:19.120> State<00:10:19.440> Management<00:10:19.959> you<00:10:20.079> got<00:10:20.160> to<00:10:20.279> know 00:10:20.389 --> 00:10:20.399 align:start position:0% context State Management you got to know 00:10:20.399 --> 00:10:22.470 align:start position:0% context State Management you got to know when<00:10:20.519> to<00:10:20.680> stop<00:10:20.880> recursing<00:10:21.839> once<00:10:22.079> again<00:10:22.240> if<00:10:22.360> you 00:10:22.470 --> 00:10:22.480 align:start position:0% when to stop recursing once again if you 00:10:22.480 --> 00:10:23.790 align:start position:0% when to stop recursing once again if you use<00:10:22.600> a<00:10:22.760> visitor<00:10:23.120> pattern<00:10:23.440> where<00:10:23.519> you've<00:10:23.680> got 00:10:23.790 --> 00:10:23.800 align:start position:0% use a visitor pattern where you've got 00:10:23.800 --> 00:10:26.750 align:start position:0% use a visitor pattern where you've got an<00:10:24.040> external<00:10:25.040> visitor<00:10:25.560> driving<00:10:26.360> external 00:10:26.750 --> 00:10:26.760 align:start position:0% an external visitor driving external 00:10:26.760 --> 00:10:28.910 align:start position:0% an external visitor driving external code<00:10:27.040> driving<00:10:27.360> your<00:10:27.519> visitor<00:10:28.399> you<00:10:28.600> often<00:10:28.800> want 00:10:28.910 --> 00:10:28.920 align:start position:0% code driving your visitor you often want 00:10:28.920 --> 00:10:30.949 align:start position:0% code driving your visitor you often want to<00:10:29.040> stop<00:10:29.360> top<00:10:29.680> or<00:10:29.839> you<00:10:30.000> don't<00:10:30.200> want<00:10:30.320> to<00:10:30.560> go<00:10:30.720> into 00:10:30.949 --> 00:10:30.959 align:start position:0% to stop top or you don't want to go into 00:10:30.959 --> 00:10:32.550 align:start position:0% to stop top or you don't want to go into the<00:10:31.079> children<00:10:31.360> of<00:10:31.519> this<00:10:31.640> node<00:10:32.000> how<00:10:32.079> do<00:10:32.200> you<00:10:32.360> do 00:10:32.550 --> 00:10:32.560 align:start position:0% the children of this node how do you do 00:10:32.560 --> 00:10:34.870 align:start position:0% the children of this node how do you do that<00:10:33.440> that<00:10:33.560> means<00:10:34.079> you<00:10:34.240> end<00:10:34.399> up<00:10:34.519> with<00:10:34.640> a<00:10:34.720> more 00:10:34.870 --> 00:10:34.880 align:start position:0% that that means you end up with a more 00:10:34.880 --> 00:10:38.030 align:start position:0% that that means you end up with a more complicated<00:10:35.839> API<00:10:36.839> State<00:10:37.279> tracking<00:10:37.600> is<00:10:37.760> quite 00:10:38.030 --> 00:10:38.040 align:start position:0% complicated API State tracking is quite 00:10:38.040 --> 00:10:39.470 align:start position:0% complicated API State tracking is quite complex<00:10:38.399> you<00:10:38.480> need<00:10:38.639> to<00:10:38.760> keep<00:10:38.959> track<00:10:39.160> of<00:10:39.279> the 00:10:39.470 --> 00:10:39.480 align:start position:0% complex you need to keep track of the 00:10:39.480 --> 00:10:43.150 align:start position:0% complex you need to keep track of the parent<00:10:39.839> node<00:10:40.600> when<00:10:40.760> you're<00:10:41.519> um<00:10:42.519> uh<00:10:42.639> walking<00:10:42.959> a 00:10:43.150 --> 00:10:43.160 align:start position:0% parent node when you're um uh walking a 00:10:43.160 --> 00:10:44.750 align:start position:0% parent node when you're um uh walking a tree<00:10:43.519> you<00:10:43.639> need<00:10:43.800> to<00:10:43.920> maintain<00:10:44.360> scope 00:10:44.750 --> 00:10:44.760 align:start position:0% tree you need to maintain scope 00:10:44.760 --> 00:10:46.629 align:start position:0% tree you need to maintain scope information<00:10:45.279> in<00:10:45.360> the<00:10:45.440> case<00:10:45.600> of<00:10:45.720> a<00:10:45.880> compiler 00:10:46.629 --> 00:10:46.639 align:start position:0% information in the case of a compiler 00:10:46.639 --> 00:10:48.550 align:start position:0% information in the case of a compiler build<00:10:46.880> up<00:10:47.000> your<00:10:47.200> composite<00:10:47.680> results<00:10:48.240> handle 00:10:48.550 --> 00:10:48.560 align:start position:0% build up your composite results handle 00:10:48.560 --> 00:10:50.910 align:start position:0% build up your composite results handle cross<00:10:48.880> node<00:10:49.279> relationships<00:10:50.279> I.E<00:10:50.639> you<00:10:50.720> want<00:10:50.839> to 00:10:50.910 --> 00:10:50.920 align:start position:0% cross node relationships I.E you want to 00:10:50.920 --> 00:10:53.470 align:start position:0% cross node relationships I.E you want to link<00:10:51.200> this<00:10:51.360> node<00:10:51.959> which<00:10:52.079> you<00:10:52.320> visited<00:10:53.320> you 00:10:53.470 --> 00:10:53.480 align:start position:0% link this node which you visited you 00:10:53.480 --> 00:10:56.030 align:start position:0% link this node which you visited you know<00:10:54.160> 30<00:10:54.519> minutes<00:10:54.839> ago<00:10:55.279> with<00:10:55.440> this<00:10:55.560> other<00:10:55.760> node 00:10:56.030 --> 00:10:56.040 align:start position:0% know 30 minutes ago with this other node 00:10:56.040 --> 00:10:57.310 align:start position:0% know 30 minutes ago with this other node which<00:10:56.160> you're<00:10:56.320> visiting 00:10:57.310 --> 00:10:57.320 align:start position:0% which you're visiting 00:10:57.320 --> 00:11:02.310 align:start position:0% which you're visiting now<00:10:58.320> now<00:10:58.519> error<00:10:58.839> handling<00:10:59.399> multiplies<00:10:59.920> the 00:11:02.310 --> 00:11:02.320 align:start position:0% 00:11:02.320 --> 00:11:04.949 align:start position:0% complexity<00:11:03.320> and<00:11:03.480> edge<00:11:03.800> cases<00:11:04.240> keep<00:11:04.480> appearing 00:11:04.949 --> 00:11:04.959 align:start position:0% complexity and edge cases keep appearing 00:11:04.959 --> 00:11:07.750 align:start position:0% complexity and edge cases keep appearing for<00:11:05.120> example<00:11:05.800> parenthesized<00:11:06.760> Expressions 00:11:07.750 --> 00:11:07.760 align:start position:0% for example parenthesized Expressions 00:11:07.760 --> 00:11:11.030 align:start position:0% for example parenthesized Expressions nested<00:11:08.240> structures<00:11:08.959> optional<00:11:09.639> elements<00:11:10.639> and 00:11:11.030 --> 00:11:11.040 align:start position:0% nested structures optional elements and 00:11:11.040 --> 00:11:13.350 align:start position:0% nested structures optional elements and language<00:11:11.480> specific<00:11:11.880> quirks<00:11:12.880> of<00:11:13.040> which<00:11:13.240> there 00:11:13.350 --> 00:11:13.360 align:start position:0% language specific quirks of which there 00:11:13.360 --> 00:11:14.949 align:start position:0% language specific quirks of which there are<00:11:13.600> plenty<00:11:13.920> in 00:11:14.949 --> 00:11:14.959 align:start position:0% are plenty in 00:11:14.959 --> 00:11:17.150 align:start position:0% are plenty in solidity<00:11:15.959> and<00:11:16.160> finally<00:11:16.600> you've<00:11:16.760> got<00:11:16.880> a<00:11:17.000> big 00:11:17.150 --> 00:11:17.160 align:start position:0% solidity and finally you've got a big 00:11:17.160 --> 00:11:19.150 align:start position:0% solidity and finally you've got a big maintenance<00:11:17.680> budget<00:11:18.200> now<00:11:18.360> I<00:11:18.480> know<00:11:18.680> I'm 00:11:19.150 --> 00:11:19.160 align:start position:0% maintenance budget now I know I'm 00:11:19.160 --> 00:11:21.430 align:start position:0% maintenance budget now I know I'm repeating<00:11:19.760> this<00:11:19.959> point<00:11:20.600> but<00:11:20.839> this<00:11:21.000> is 00:11:21.430 --> 00:11:21.440 align:start position:0% repeating this point but this is 00:11:21.440 --> 00:11:22.870 align:start position:0% repeating this point but this is significant<00:11:21.959> as<00:11:22.079> you'll<00:11:22.200> see<00:11:22.399> when<00:11:22.519> we<00:11:22.639> get<00:11:22.760> to 00:11:22.870 --> 00:11:22.880 align:start position:0% significant as you'll see when we get to 00:11:22.880 --> 00:11:26.910 align:start position:0% significant as you'll see when we get to queries<00:11:23.560> which<00:11:23.720> I<00:11:23.839> think<00:11:23.959> is<00:11:24.079> the<00:11:24.279> next 00:11:26.910 --> 00:11:26.920 align:start position:0% 00:11:26.920 --> 00:11:31.750 align:start position:0% slide<00:11:27.920> so<00:11:28.200> this<00:11:28.320> is<00:11:28.600> where<00:11:29.480> queries<00:11:30.240> come<00:11:30.760> in 00:11:31.750 --> 00:11:31.760 align:start position:0% slide so this is where queries come in 00:11:31.760 --> 00:11:33.710 align:start position:0% slide so this is where queries come in so<00:11:32.120> let's<00:11:32.360> look<00:11:32.480> at<00:11:32.639> how<00:11:32.800> we<00:11:32.959> solve<00:11:33.320> some<00:11:33.480> of 00:11:33.710 --> 00:11:33.720 align:start position:0% so let's look at how we solve some of 00:11:33.720 --> 00:11:37.150 align:start position:0% so let's look at how we solve some of those<00:11:34.160> same<00:11:34.680> problems<00:11:35.600> using<00:11:35.959> queries<00:11:36.839> so 00:11:37.150 --> 00:11:37.160 align:start position:0% those same problems using queries so 00:11:37.160 --> 00:11:38.670 align:start position:0% those same problems using queries so this<00:11:37.320> is<00:11:37.440> our<00:11:37.639> first<00:11:37.920> example<00:11:38.360> we<00:11:38.440> want<00:11:38.560> to 00:11:38.670 --> 00:11:38.680 align:start position:0% this is our first example we want to 00:11:38.680 --> 00:11:41.389 align:start position:0% this is our first example we want to find<00:11:38.920> all<00:11:39.040> the<00:11:39.200> unit<00:11:39.560> variable<00:11:40.560> uh<00:11:40.959> all<00:11:41.160> the 00:11:41.389 --> 00:11:41.399 align:start position:0% find all the unit variable uh all the 00:11:41.399 --> 00:11:43.389 align:start position:0% find all the unit variable uh all the uint<00:11:41.959> variable 00:11:43.389 --> 00:11:43.399 align:start position:0% uint variable 00:11:43.399 --> 00:11:46.150 align:start position:0% uint variable declarations<00:11:44.399> it's<00:11:44.560> as<00:11:44.720> simple<00:11:45.000> as<00:11:45.160> saying 00:11:46.150 --> 00:11:46.160 align:start position:0% declarations it's as simple as saying 00:11:46.160 --> 00:11:48.150 align:start position:0% declarations it's as simple as saying inv<00:11:46.480> variable<00:11:46.880> declarations<00:11:47.560> where<00:11:47.760> the<00:11:47.920> type 00:11:48.150 --> 00:11:48.160 align:start position:0% inv variable declarations where the type 00:11:48.160 --> 00:11:51.190 align:start position:0% inv variable declarations where the type name<00:11:48.360> is<00:11:48.519> uint<00:11:49.480> and<00:11:49.600> it's<00:11:49.800> got<00:11:49.920> an<00:11:50.200> identifier 00:11:51.190 --> 00:11:51.200 align:start position:0% name is uint and it's got an identifier 00:11:51.200 --> 00:11:55.670 align:start position:0% name is uint and it's got an identifier bind<00:11:51.560> that<00:11:51.680> and<00:11:52.000> return<00:11:52.200> it<00:11:52.880> no 00:11:55.670 --> 00:11:55.680 align:start position:0% 00:11:55.680 --> 00:11:58.870 align:start position:0% traversal<00:11:56.680> no<00:11:56.959> edge<00:11:57.399> cases<00:11:58.399> hardly<00:11:58.720> any 00:11:58.870 --> 00:11:58.880 align:start position:0% traversal no edge cases hardly any 00:11:58.880 --> 00:12:01.670 align:start position:0% traversal no edge cases hardly any maintenance<00:11:59.680> no<00:11:59.959> efficiency<00:12:00.480> problems<00:12:01.480> so 00:12:01.670 --> 00:12:01.680 align:start position:0% maintenance no efficiency problems so 00:12:01.680 --> 00:12:03.310 align:start position:0% maintenance no efficiency problems so the<00:12:01.880> second<00:12:02.200> example<00:12:02.560> shows<00:12:02.839> something<00:12:03.079> a<00:12:03.200> bit 00:12:03.310 --> 00:12:03.320 align:start position:0% the second example shows something a bit 00:12:03.320 --> 00:12:05.310 align:start position:0% the second example shows something a bit more<00:12:03.519> powerful<00:12:04.399> in<00:12:04.560> this<00:12:04.720> case<00:12:04.920> we<00:12:05.040> want<00:12:05.160> to 00:12:05.310 --> 00:12:05.320 align:start position:0% more powerful in this case we want to 00:12:05.320 --> 00:12:06.829 align:start position:0% more powerful in this case we want to find<00:12:05.600> immediately<00:12:06.079> nested<00:12:06.519> function 00:12:06.829 --> 00:12:06.839 align:start position:0% find immediately nested function 00:12:06.839 --> 00:12:09.069 align:start position:0% find immediately nested function declarations<00:12:07.519> are<00:12:07.839> a<00:12:07.959> function<00:12:08.680> inside 00:12:09.069 --> 00:12:09.079 align:start position:0% declarations are a function inside 00:12:09.079 --> 00:12:09.949 align:start position:0% declarations are a function inside another 00:12:09.949 --> 00:12:09.959 align:start position:0% another 00:12:09.959 --> 00:12:13.069 align:start position:0% another function<00:12:10.959> so<00:12:11.240> here<00:12:11.399> we're<00:12:11.600> saying<00:12:12.600> in<00:12:12.800> every 00:12:13.069 --> 00:12:13.079 align:start position:0% function so here we're saying in every 00:12:13.079 --> 00:12:14.750 align:start position:0% function so here we're saying in every contract<00:12:13.519> definition<00:12:14.320> there<00:12:14.399> are<00:12:14.560> some 00:12:14.750 --> 00:12:14.760 align:start position:0% contract definition there are some 00:12:14.760 --> 00:12:17.230 align:start position:0% contract definition there are some contract<00:12:15.320> members<00:12:16.320> in<00:12:16.480> the<00:12:16.639> contract<00:12:16.959> members 00:12:17.230 --> 00:12:17.240 align:start position:0% contract members in the contract members 00:12:17.240 --> 00:12:19.829 align:start position:0% contract members in the contract members is<00:12:17.399> a<00:12:17.560> contract<00:12:17.959> member<00:12:18.959> for<00:12:19.199> every<00:12:19.440> function 00:12:19.829 --> 00:12:19.839 align:start position:0% is a contract member for every function 00:12:19.839 --> 00:12:21.949 align:start position:0% is a contract member for every function definition<00:12:20.240> in<00:12:20.440> there<00:12:20.639> find<00:12:20.880> the<00:12:21.040> block<00:12:21.800> and 00:12:21.949 --> 00:12:21.959 align:start position:0% definition in there find the block and 00:12:21.959 --> 00:12:24.069 align:start position:0% definition in there find the block and look<00:12:22.120> for<00:12:22.360> the<00:12:22.920> a<00:12:23.199> statement<00:12:23.600> in<00:12:23.760> there<00:12:23.959> that 00:12:24.069 --> 00:12:24.079 align:start position:0% look for the a statement in there that 00:12:24.079 --> 00:12:27.150 align:start position:0% look for the a statement in there that is<00:12:24.240> a<00:12:24.519> itself<00:12:24.800> a<00:12:24.959> function<00:12:25.760> definition<00:12:26.760> call 00:12:27.150 --> 00:12:27.160 align:start position:0% is a itself a function definition call 00:12:27.160 --> 00:12:29.790 align:start position:0% is a itself a function definition call bind<00:12:27.399> that<00:12:27.519> to<00:12:27.639> a<00:12:27.760> variable<00:12:28.720> called<00:12:29.199> tested 00:12:29.790 --> 00:12:29.800 align:start position:0% bind that to a variable called tested 00:12:29.800 --> 00:12:31.509 align:start position:0% bind that to a variable called tested and<00:12:30.120> return 00:12:31.509 --> 00:12:31.519 align:start position:0% and return 00:12:31.519 --> 00:12:34.269 align:start position:0% and return it<00:12:32.519> so<00:12:32.959> why<00:12:33.079> is<00:12:33.199> this<00:12:33.360> so<00:12:33.560> powerful<00:12:33.959> well<00:12:34.120> first 00:12:34.269 --> 00:12:34.279 align:start position:0% it so why is this so powerful well first 00:12:34.279 --> 00:12:36.189 align:start position:0% it so why is this so powerful well first of<00:12:34.399> all<00:12:34.560> it's<00:12:34.760> declarative<00:12:35.440> we<00:12:35.560> it's<00:12:35.760> saying 00:12:36.189 --> 00:12:36.199 align:start position:0% of all it's declarative we it's saying 00:12:36.199 --> 00:12:39.629 align:start position:0% of all it's declarative we it's saying what<00:12:36.360> we<00:12:36.560> want<00:12:37.160> not<00:12:37.440> how<00:12:37.639> we<00:12:37.760> want<00:12:37.920> to<00:12:38.079> do<00:12:38.639> it 00:12:39.629 --> 00:12:39.639 align:start position:0% what we want not how we want to do it 00:12:39.639 --> 00:12:41.790 align:start position:0% what we want not how we want to do it makes<00:12:39.880> that<00:12:40.079> code<00:12:40.320> easier<00:12:40.639> to<00:12:41.040> understand<00:12:41.199> and 00:12:41.790 --> 00:12:41.800 align:start position:0% makes that code easier to understand and 00:12:41.800 --> 00:12:43.829 align:start position:0% makes that code easier to understand and maintain<00:12:42.800> and<00:12:42.959> when<00:12:43.079> you<00:12:43.199> look<00:12:43.360> at<00:12:43.519> this<00:12:43.639> two 00:12:43.829 --> 00:12:43.839 align:start position:0% maintain and when you look at this two 00:12:43.839 --> 00:12:45.230 align:start position:0% maintain and when you look at this two months<00:12:44.079> later<00:12:44.360> it's<00:12:44.560> obvious<00:12:44.880> what<00:12:45.000> it's 00:12:45.230 --> 00:12:45.240 align:start position:0% months later it's obvious what it's 00:12:45.240 --> 00:12:47.389 align:start position:0% months later it's obvious what it's doing<00:12:46.160> whereas<00:12:46.480> I'd<00:12:46.680> suggest<00:12:47.040> that<00:12:47.160> you'd 00:12:47.389 --> 00:12:47.399 align:start position:0% doing whereas I'd suggest that you'd 00:12:47.399 --> 00:12:50.030 align:start position:0% doing whereas I'd suggest that you'd have<00:12:47.560> a<00:12:47.639> couple<00:12:47.880> of<00:12:48.079> pages<00:12:48.399> of<00:12:49.040> code 00:12:50.030 --> 00:12:50.040 align:start position:0% have a couple of pages of code 00:12:50.040 --> 00:12:52.550 align:start position:0% have a couple of pages of code traversing<00:12:50.560> your<00:12:50.760> tree<00:12:51.639> if<00:12:51.760> you<00:12:51.880> were<00:12:52.040> using 00:12:52.550 --> 00:12:52.560 align:start position:0% traversing your tree if you were using 00:12:52.560 --> 00:12:54.670 align:start position:0% traversing your tree if you were using manual<00:12:52.920> traversal<00:12:53.920> and<00:12:54.040> it<00:12:54.160> wouldn't<00:12:54.480> be 00:12:54.670 --> 00:12:54.680 align:start position:0% manual traversal and it wouldn't be 00:12:54.680 --> 00:12:56.590 align:start position:0% manual traversal and it wouldn't be obvious<00:12:55.079> what<00:12:55.199> it<00:12:55.279> was<00:12:55.480> actually<00:12:55.680> meant<00:12:55.880> to 00:12:56.590 --> 00:12:56.600 align:start position:0% obvious what it was actually meant to 00:12:56.600 --> 00:13:00.269 align:start position:0% obvious what it was actually meant to do<00:12:57.600> so<00:12:57.920> it's<00:12:58.120> structure<00:12:58.639> aware 00:13:00.269 --> 00:13:00.279 align:start position:0% do so it's structure aware 00:13:00.279 --> 00:13:03.590 align:start position:0% do so it's structure aware so<00:13:00.839> the<00:13:00.959> query<00:13:01.680> understands<00:13:02.199> solidity<00:13:03.120> syntax 00:13:03.590 --> 00:13:03.600 align:start position:0% so the query understands solidity syntax 00:13:03.600 --> 00:13:05.790 align:start position:0% so the query understands solidity syntax structure<00:13:04.560> it<00:13:04.680> knows<00:13:04.959> about<00:13:05.240> scope<00:13:05.560> and<00:13:05.680> it 00:13:05.790 --> 00:13:05.800 align:start position:0% structure it knows about scope and it 00:13:05.800 --> 00:13:08.150 align:start position:0% structure it knows about scope and it knows<00:13:06.040> about<00:13:06.399> nesting<00:13:07.399> and<00:13:07.480> it<00:13:07.639> also<00:13:07.880> knows 00:13:08.150 --> 00:13:08.160 align:start position:0% knows about nesting and it also knows 00:13:08.160 --> 00:13:10.269 align:start position:0% knows about nesting and it also knows where<00:13:08.399> type<00:13:08.680> name<00:13:08.959> for<00:13:09.120> example<00:13:09.800> in<00:13:09.959> the<00:13:10.199> in 00:13:10.269 --> 00:13:10.279 align:start position:0% where type name for example in the in 00:13:10.279 --> 00:13:14.910 align:start position:0% where type name for example in the in the<00:13:10.440> first<00:13:10.720> case<00:13:11.040> here<00:13:11.600> appears<00:13:11.920> in<00:13:12.040> the 00:13:14.910 --> 00:13:14.920 align:start position:0% 00:13:14.920 --> 00:13:18.710 align:start position:0% tree<00:13:15.920> these<00:13:16.160> patterns<00:13:16.639> are<00:13:17.360> composable<00:13:18.360> so<00:13:18.600> we 00:13:18.710 --> 00:13:18.720 align:start position:0% tree these patterns are composable so we 00:13:18.720 --> 00:13:21.629 align:start position:0% tree these patterns are composable so we can<00:13:18.880> build<00:13:19.560> complex<00:13:20.519> pattern<00:13:20.839> matching<00:13:21.360> from 00:13:21.629 --> 00:13:21.639 align:start position:0% can build complex pattern matching from 00:13:21.639 --> 00:13:23.870 align:start position:0% can build complex pattern matching from simple<00:13:22.000> pattern<00:13:22.320> matching<00:13:23.279> so<00:13:23.480> if<00:13:23.600> we<00:13:23.680> wanted 00:13:23.870 --> 00:13:23.880 align:start position:0% simple pattern matching so if we wanted 00:13:23.880 --> 00:13:25.790 align:start position:0% simple pattern matching so if we wanted to<00:13:24.040> find<00:13:24.279> uint<00:13:24.720> variables<00:13:25.320> Within<00:13:25.639> These 00:13:25.790 --> 00:13:25.800 align:start position:0% to find uint variables Within These 00:13:25.800 --> 00:13:27.990 align:start position:0% to find uint variables Within These nested<00:13:26.240> function<00:13:26.680> definitions<00:13:27.560> it<00:13:27.680> would<00:13:27.839> be 00:13:27.990 --> 00:13:28.000 align:start position:0% nested function definitions it would be 00:13:28.000 --> 00:13:30.829 align:start position:0% nested function definitions it would be as<00:13:28.160> simple<00:13:28.480> as<00:13:28.920> put<00:13:29.120> putting<00:13:29.399> that<00:13:30.160> appending 00:13:30.829 --> 00:13:30.839 align:start position:0% as simple as put putting that appending 00:13:30.839 --> 00:13:35.269 align:start position:0% as simple as put putting that appending that<00:13:31.839> first<00:13:32.519> query<00:13:33.519> below<00:13:33.839> the<00:13:33.959> second<00:13:34.279> query 00:13:35.269 --> 00:13:35.279 align:start position:0% that first query below the second query 00:13:35.279 --> 00:13:36.350 align:start position:0% that first query below the second query but<00:13:35.519> most 00:13:36.350 --> 00:13:36.360 align:start position:0% but most 00:13:36.360 --> 00:13:38.990 align:start position:0% but most importantly<00:13:37.360> this<00:13:37.560> is<00:13:37.920> focusing<00:13:38.480> once<00:13:38.760> again 00:13:38.990 --> 00:13:39.000 align:start position:0% importantly this is focusing once again 00:13:39.000 --> 00:13:41.350 align:start position:0% importantly this is focusing once again on<00:13:39.279> what<00:13:39.480> we're<00:13:39.680> trying<00:13:39.920> to<00:13:40.120> achieve<00:13:41.079> we<00:13:41.199> can 00:13:41.350 --> 00:13:41.360 align:start position:0% on what we're trying to achieve we can 00:13:41.360 --> 00:13:43.269 align:start position:0% on what we're trying to achieve we can think<00:13:41.560> about<00:13:41.880> code<00:13:42.199> patterns<00:13:42.600> and<00:13:42.800> structure 00:13:43.269 --> 00:13:43.279 align:start position:0% think about code patterns and structure 00:13:43.279 --> 00:13:45.430 align:start position:0% think about code patterns and structure design<00:13:44.079> without<00:13:44.360> getting<00:13:44.639> bobbed<00:13:45.120> bogged 00:13:45.430 --> 00:13:45.440 align:start position:0% design without getting bobbed bogged 00:13:45.440 --> 00:13:47.069 align:start position:0% design without getting bobbed bogged down<00:13:45.600> in<00:13:45.720> the<00:13:45.839> implementation 00:13:47.069 --> 00:13:47.079 align:start position:0% down in the implementation 00:13:47.079 --> 00:13:49.069 align:start position:0% down in the implementation details<00:13:48.079> so<00:13:48.399> let's<00:13:48.560> have<00:13:48.680> a<00:13:48.760> look<00:13:48.880> at<00:13:48.959> some 00:13:49.069 --> 00:13:49.079 align:start position:0% details so let's have a look at some 00:13:49.079 --> 00:13:50.509 align:start position:0% details so let's have a look at some more<00:13:49.240> advanced<00:13:49.639> query 00:13:50.509 --> 00:13:50.519 align:start position:0% more advanced query 00:13:50.519 --> 00:13:52.629 align:start position:0% more advanced query patterns<00:13:51.519> this<00:13:51.639> one<00:13:51.839> for<00:13:52.199> well<00:13:52.399> this<00:13:52.519> one 00:13:52.629 --> 00:13:52.639 align:start position:0% patterns this one for well this one 00:13:52.639 --> 00:13:54.670 align:start position:0% patterns this one for well this one isn't<00:13:52.880> that<00:13:53.040> advanced<00:13:53.600> but<00:13:54.040> for<00:13:54.199> example<00:13:54.519> in 00:13:54.670 --> 00:13:54.680 align:start position:0% isn't that advanced but for example in 00:13:54.680 --> 00:13:56.189 align:start position:0% isn't that advanced but for example in an<00:13:54.839> unchecked<00:13:55.279> block<00:13:55.480> you<00:13:55.560> want<00:13:55.680> to<00:13:55.800> find<00:13:56.000> all 00:13:56.189 --> 00:13:56.199 align:start position:0% an unchecked block you want to find all 00:13:56.199 --> 00:13:58.470 align:start position:0% an unchecked block you want to find all function<00:13:56.560> calls<00:13:57.360> as<00:13:57.519> easy<00:13:57.800> of<00:13:57.959> that<00:13:58.120> and<00:13:58.240> it's 00:13:58.470 --> 00:13:58.480 align:start position:0% function calls as easy of that and it's 00:13:58.480 --> 00:14:00.150 align:start position:0% function calls as easy of that and it's obvious<00:13:58.839> what<00:13:59.160> it<00:13:59.279> does<00:13:59.639> you<00:13:59.759> could<00:13:59.920> write 00:14:00.150 --> 00:14:00.160 align:start position:0% obvious what it does you could write 00:14:00.160 --> 00:14:03.629 align:start position:0% obvious what it does you could write this<00:14:00.279> on<00:14:00.440> one 00:14:03.629 --> 00:14:03.639 align:start position:0% 00:14:03.639 --> 00:14:06.389 align:start position:0% line<00:14:04.639> the<00:14:04.800> second<00:14:05.120> example<00:14:05.680> is<00:14:05.839> a<00:14:06.000> bit<00:14:06.160> more 00:14:06.389 --> 00:14:06.399 align:start position:0% line the second example is a bit more 00:14:06.399 --> 00:14:08.470 align:start position:0% line the second example is a bit more complicated<00:14:07.360> but<00:14:07.560> here<00:14:07.720> we're<00:14:07.959> looking<00:14:08.199> for 00:14:08.470 --> 00:14:08.480 align:start position:0% complicated but here we're looking for 00:14:08.480 --> 00:14:09.470 align:start position:0% complicated but here we're looking for variable 00:14:09.470 --> 00:14:09.480 align:start position:0% variable 00:14:09.480 --> 00:14:11.350 align:start position:0% variable declarations<00:14:10.480> uh<00:14:10.600> State<00:14:10.920> variable 00:14:11.350 --> 00:14:11.360 align:start position:0% declarations uh State variable 00:14:11.360 --> 00:14:13.110 align:start position:0% declarations uh State variable declarations<00:14:12.160> that<00:14:12.279> have<00:14:12.399> a<00:14:12.600> type<00:14:12.839> that<00:14:12.959> is 00:14:13.110 --> 00:14:13.120 align:start position:0% declarations that have a type that is 00:14:13.120 --> 00:14:18.710 align:start position:0% declarations that have a type that is either<00:14:13.399> map<00:14:13.759> a<00:14:13.880> mapping<00:14:14.680> or<00:14:14.880> an 00:14:18.710 --> 00:14:18.720 align:start position:0% 00:14:18.720 --> 00:14:20.749 align:start position:0% array<00:14:19.720> and<00:14:19.880> think<00:14:20.079> about<00:14:20.320> what<00:14:20.440> this<00:14:20.560> would 00:14:20.749 --> 00:14:20.759 align:start position:0% array and think about what this would 00:14:20.759 --> 00:14:22.949 align:start position:0% array and think about what this would take<00:14:20.959> if<00:14:21.079> you<00:14:21.279> doing<00:14:21.480> manual<00:14:21.800> traversal<00:14:22.759> You' 00:14:22.949 --> 00:14:22.959 align:start position:0% take if you doing manual traversal You' 00:14:22.959 --> 00:14:25.470 align:start position:0% take if you doing manual traversal You' need<00:14:23.160> scope<00:14:23.480> tracking<00:14:24.079> type<00:14:24.320> checking<00:14:24.680> logic 00:14:25.470 --> 00:14:25.480 align:start position:0% need scope tracking type checking logic 00:14:25.480 --> 00:14:28.150 align:start position:0% need scope tracking type checking logic complex<00:14:26.120> conditional<00:14:26.680> logic<00:14:27.680> and<00:14:27.800> you'd<00:14:28.000> need 00:14:28.150 --> 00:14:28.160 align:start position:0% complex conditional logic and you'd need 00:14:28.160 --> 00:14:30.230 align:start position:0% complex conditional logic and you'd need to<00:14:28.399> hand<00:14:28.600> carefully<00:14:29.160> handle<00:14:29.519> the<00:14:29.800> nested 00:14:30.230 --> 00:14:30.240 align:start position:0% to hand carefully handle the nested 00:14:30.240 --> 00:14:34.030 align:start position:0% to hand carefully handle the nested structure 00:14:34.030 --> 00:14:34.040 align:start position:0% 00:14:34.040 --> 00:14:37.269 align:start position:0% here<00:14:35.040> so<00:14:35.360> what<00:14:35.480> are<00:14:35.639> the<00:14:35.920> use<00:14:36.240> cases<00:14:36.600> for<00:14:36.800> this 00:14:37.269 --> 00:14:37.279 align:start position:0% here so what are the use cases for this 00:14:37.279 --> 00:14:39.069 align:start position:0% here so what are the use cases for this or<00:14:37.440> some<00:14:37.720> use<00:14:38.040> cases<00:14:38.360> CU<00:14:38.519> I'm<00:14:38.639> hoping<00:14:38.920> that 00:14:39.069 --> 00:14:39.079 align:start position:0% or some use cases CU I'm hoping that 00:14:39.079 --> 00:14:41.629 align:start position:0% or some use cases CU I'm hoping that people<00:14:39.320> come<00:14:39.519> up<00:14:39.720> with<00:14:40.600> far<00:14:40.800> more<00:14:41.000> use<00:14:41.320> cases 00:14:41.629 --> 00:14:41.639 align:start position:0% people come up with far more use cases 00:14:41.639 --> 00:14:44.310 align:start position:0% people come up with far more use cases than<00:14:41.800> we<00:14:41.959> know<00:14:42.440> we<00:14:42.600> want<00:14:42.880> sort<00:14:43.079> of<00:14:43.639> emergent 00:14:44.310 --> 00:14:44.320 align:start position:0% than we know we want sort of emergent 00:14:44.320 --> 00:14:47.790 align:start position:0% than we know we want sort of emergent benefits<00:14:44.759> from<00:14:45.120> this<00:14:46.120> well<00:14:47.040> if<00:14:47.160> you<00:14:47.279> wanted<00:14:47.560> to 00:14:47.790 --> 00:14:47.800 align:start position:0% benefits from this well if you wanted to 00:14:47.800 --> 00:14:49.470 align:start position:0% benefits from this well if you wanted to have<00:14:48.040> custom<00:14:48.399> coding<00:14:48.720> standards<00:14:49.120> you<00:14:49.199> want<00:14:49.320> to 00:14:49.470 --> 00:14:49.480 align:start position:0% have custom coding standards you want to 00:14:49.480 --> 00:14:51.590 align:start position:0% have custom coding standards you want to enforce<00:14:49.839> custom<00:14:50.160> coding<00:14:50.560> standards<00:14:51.399> you've 00:14:51.590 --> 00:14:51.600 align:start position:0% enforce custom coding standards you've 00:14:51.600 --> 00:14:53.509 align:start position:0% enforce custom coding standards you've got<00:14:51.880> project<00:14:52.320> specific<00:14:52.759> restrictions<00:14:53.399> that 00:14:53.509 --> 00:14:53.519 align:start position:0% got project specific restrictions that 00:14:53.519 --> 00:14:55.710 align:start position:0% got project specific restrictions that you<00:14:53.639> want<00:14:53.759> to<00:14:54.040> check<00:14:55.040> or<00:14:55.199> you<00:14:55.279> want<00:14:55.399> to<00:14:55.480> do 00:14:55.710 --> 00:14:55.720 align:start position:0% you want to check or you want to do 00:14:55.720 --> 00:14:57.310 align:start position:0% you want to check or you want to do version<00:14:56.079> compatibility<00:14:56.720> check<00:14:57.000> so<00:14:57.120> you<00:14:57.199> want 00:14:57.310 --> 00:14:57.320 align:start position:0% version compatibility check so you want 00:14:57.320 --> 00:14:58.749 align:start position:0% version compatibility check so you want to<00:14:57.440> make<00:14:57.600> sure<00:14:57.800> that<00:14:57.920> you<00:14:58.040> don't<00:14:58.240> use<00:14:58.480> certain 00:14:58.749 --> 00:14:58.759 align:start position:0% to make sure that you don't use certain 00:14:58.759 --> 00:15:02.230 align:start position:0% to make sure that you don't use certain featur<00:14:59.040> pies<00:14:59.279> of 00:15:02.230 --> 00:15:02.240 align:start position:0% 00:15:02.240 --> 00:15:04.509 align:start position:0% solidity<00:15:03.240> uh<00:15:03.440> style<00:15:03.800> checking<00:15:04.279> well<00:15:04.399> if 00:15:04.509 --> 00:15:04.519 align:start position:0% solidity uh style checking well if 00:15:04.519 --> 00:15:06.230 align:start position:0% solidity uh style checking well if you've<00:15:04.720> got<00:15:05.000> specific<00:15:05.399> naming<00:15:05.800> patterns<00:15:06.120> you 00:15:06.230 --> 00:15:06.240 align:start position:0% you've got specific naming patterns you 00:15:06.240 --> 00:15:08.829 align:start position:0% you've got specific naming patterns you want<00:15:06.360> to<00:15:06.759> enforce<00:15:07.759> uh<00:15:07.959> specific<00:15:08.360> structural 00:15:08.829 --> 00:15:08.839 align:start position:0% want to enforce uh specific structural 00:15:08.839 --> 00:15:10.829 align:start position:0% want to enforce uh specific structural conventions<00:15:09.839> and<00:15:09.959> you<00:15:10.040> can<00:15:10.199> have<00:15:10.399> context 00:15:10.829 --> 00:15:10.839 align:start position:0% conventions and you can have context 00:15:10.839 --> 00:15:12.829 align:start position:0% conventions and you can have context Weare<00:15:11.079> rules<00:15:11.480> now<00:15:11.639> you<00:15:11.759> might<00:15:11.959> be<00:15:12.160> thinking 00:15:12.829 --> 00:15:12.839 align:start position:0% Weare rules now you might be thinking 00:15:12.839 --> 00:15:15.189 align:start position:0% Weare rules now you might be thinking well<00:15:13.079> can't<00:15:13.279> I<00:15:13.399> use<00:15:13.560> a<00:15:13.680> linter<00:15:14.040> to<00:15:14.199> do<00:15:14.440> this 00:15:15.189 --> 00:15:15.199 align:start position:0% well can't I use a linter to do this 00:15:15.199 --> 00:15:16.949 align:start position:0% well can't I use a linter to do this well<00:15:15.480> yes<00:15:15.720> but<00:15:15.880> this<00:15:16.000> is<00:15:16.160> meant<00:15:16.399> to<00:15:16.560> write<00:15:16.839> the 00:15:16.949 --> 00:15:16.959 align:start position:0% well yes but this is meant to write the 00:15:16.959 --> 00:15:19.790 align:start position:0% well yes but this is meant to write the linter<00:15:17.440> this<00:15:17.560> is<00:15:18.279> designed<00:15:18.920> for<00:15:19.360> writing 00:15:19.790 --> 00:15:19.800 align:start position:0% linter this is designed for writing 00:15:19.800 --> 00:15:21.910 align:start position:0% linter this is designed for writing linters<00:15:20.320> so<00:15:20.759> that's<00:15:20.959> why<00:15:21.199> these<00:15:21.360> are<00:15:21.480> the<00:15:21.639> use 00:15:21.910 --> 00:15:21.920 align:start position:0% linters so that's why these are the use 00:15:21.920 --> 00:15:24.030 align:start position:0% linters so that's why these are the use cases<00:15:22.600> this<00:15:22.680> is<00:15:22.839> not<00:15:23.040> an<00:15:23.160> end<00:15:23.399> user<00:15:23.680> tool<00:15:23.959> this 00:15:24.030 --> 00:15:24.040 align:start position:0% cases this is not an end user tool this 00:15:24.040 --> 00:15:29.389 align:start position:0% cases this is not an end user tool this is<00:15:24.160> a<00:15:24.320> tool<00:15:24.600> for<00:15:24.880> developers<00:15:25.880> to<00:15:26.120> write<00:15:26.600> tools 00:15:29.389 --> 00:15:29.399 align:start position:0% is a tool for developers to write tools 00:15:29.399 --> 00:15:31.910 align:start position:0% is a tool for developers to write tools uh<00:15:29.560> so<00:15:29.800> you<00:15:29.959> can<00:15:30.240> do<00:15:30.519> patent<00:15:30.800> detection<00:15:31.560> anti 00:15:31.910 --> 00:15:31.920 align:start position:0% uh so you can do patent detection anti 00:15:31.920 --> 00:15:34.670 align:start position:0% uh so you can do patent detection anti patents<00:15:32.279> for<00:15:32.759> example<00:15:33.759> uh<00:15:33.920> optimization 00:15:34.670 --> 00:15:34.680 align:start position:0% patents for example uh optimization 00:15:34.680 --> 00:15:36.030 align:start position:0% patents for example uh optimization opportunities<00:15:35.399> which<00:15:35.519> may<00:15:35.720> not<00:15:35.880> be 00:15:36.030 --> 00:15:36.040 align:start position:0% opportunities which may not be 00:15:36.040 --> 00:15:37.629 align:start position:0% opportunities which may not be immediately<00:15:36.519> obvious<00:15:36.959> if<00:15:37.040> you've<00:15:37.199> got<00:15:37.279> a<00:15:37.399> big 00:15:37.629 --> 00:15:37.639 align:start position:0% immediately obvious if you've got a big 00:15:37.639 --> 00:15:40.990 align:start position:0% immediately obvious if you've got a big library<00:15:38.560> of<00:15:38.959> things<00:15:39.959> uh<00:15:40.120> detecting<00:15:40.639> complex 00:15:40.990 --> 00:15:41.000 align:start position:0% library of things uh detecting complex 00:15:41.000 --> 00:15:42.350 align:start position:0% library of things uh detecting complex structural<00:15:41.440> patterns<00:15:41.839> that<00:15:41.920> you<00:15:42.040> might<00:15:42.240> want 00:15:42.350 --> 00:15:42.360 align:start position:0% structural patterns that you might want 00:15:42.360 --> 00:15:45.150 align:start position:0% structural patterns that you might want to<00:15:42.600> simplify<00:15:43.279> or<00:15:43.519> or<00:15:44.000> Mark<00:15:44.399> so<00:15:44.639> once<00:15:44.839> again 00:15:45.150 --> 00:15:45.160 align:start position:0% to simplify or or Mark so once again 00:15:45.160 --> 00:15:48.670 align:start position:0% to simplify or or Mark so once again this<00:15:45.240> is<00:15:45.360> a<00:15:45.480> kind<00:15:45.600> of<00:15:45.720> an<00:15:45.839> es<00:15:46.399> linter<00:15:47.399> uh 00:15:48.670 --> 00:15:48.680 align:start position:0% this is a kind of an es linter uh 00:15:48.680 --> 00:15:51.230 align:start position:0% this is a kind of an es linter uh equivalent<00:15:49.680> code<00:15:50.000> transformation<00:15:50.720> automated 00:15:51.230 --> 00:15:51.240 align:start position:0% equivalent code transformation automated 00:15:51.240 --> 00:15:52.710 align:start position:0% equivalent code transformation automated refactoring<00:15:51.920> refactoring<00:15:52.480> is 00:15:52.710 --> 00:15:52.720 align:start position:0% refactoring refactoring is 00:15:52.720 --> 00:15:55.550 align:start position:0% refactoring refactoring is Transformations<00:15:53.639> that<00:15:54.319> um<00:15:54.519> preserve<00:15:54.920> the 00:15:55.550 --> 00:15:55.560 align:start position:0% Transformations that um preserve the 00:15:55.560 --> 00:15:58.110 align:start position:0% Transformations that um preserve the semantics<00:15:56.560> uh<00:15:56.680> code<00:15:57.000> modernization<00:15:57.920> it's 00:15:58.110 --> 00:15:58.120 align:start position:0% semantics uh code modernization it's 00:15:58.120 --> 00:15:59.509 align:start position:0% semantics uh code modernization it's very<00:15:58.360> easy<00:15:58.600> to<00:15:58.759> write 00:15:59.509 --> 00:15:59.519 align:start position:0% very easy to write 00:15:59.519 --> 00:16:02.829 align:start position:0% very easy to write um<00:15:59.759> patterns<00:16:00.240> that<00:16:00.440> then<00:16:00.680> transform<00:16:01.480> into<00:16:02.480> uh 00:16:02.829 --> 00:16:02.839 align:start position:0% um patterns that then transform into uh 00:16:02.839 --> 00:16:05.470 align:start position:0% um patterns that then transform into uh more<00:16:03.120> modern<00:16:03.560> code<00:16:04.319> automated<00:16:04.839> modifications 00:16:05.470 --> 00:16:05.480 align:start position:0% more modern code automated modifications 00:16:05.480 --> 00:16:07.069 align:start position:0% more modern code automated modifications i.<00:16:05.800> things<00:16:05.959> that<00:16:06.079> aren't<00:16:06.279> refactorings<00:16:06.880> that 00:16:07.069 --> 00:16:07.079 align:start position:0% i. things that aren't refactorings that 00:16:07.079 --> 00:16:10.189 align:start position:0% i. things that aren't refactorings that actually<00:16:07.279> change<00:16:07.639> the<00:16:07.920> code<00:16:08.920> and<00:16:09.199> formatting 00:16:10.189 --> 00:16:10.199 align:start position:0% actually change the code and formatting 00:16:10.199 --> 00:16:14.189 align:start position:0% actually change the code and formatting and<00:16:10.399> as<00:16:10.519> I<00:16:10.720> said<00:16:11.720> uh<00:16:11.920> pretty<00:16:12.800> solidity<00:16:13.800> is 00:16:14.189 --> 00:16:14.199 align:start position:0% and as I said uh pretty solidity is 00:16:14.199 --> 00:16:17.870 align:start position:0% and as I said uh pretty solidity is already<00:16:14.600> using<00:16:15.600> uh 00:16:17.870 --> 00:16:17.880 align:start position:0% 00:16:17.880 --> 00:16:20.309 align:start position:0% slang<00:16:18.880> uh<00:16:19.079> one<00:16:19.440> important<00:16:19.839> point<00:16:20.000> I<00:16:20.079> want<00:16:20.199> to 00:16:20.309 --> 00:16:20.319 align:start position:0% slang uh one important point I want to 00:16:20.319 --> 00:16:25.470 align:start position:0% slang uh one important point I want to make<00:16:20.600> here<00:16:20.920> is<00:16:21.399> that<00:16:22.560> uh<00:16:23.560> we<00:16:23.800> support<00:16:24.279> WM<00:16:25.279> and 00:16:25.470 --> 00:16:25.480 align:start position:0% make here is that uh we support WM and 00:16:25.480 --> 00:16:27.749 align:start position:0% make here is that uh we support WM and we<00:16:25.680> support<00:16:26.079> in<00:16:26.319> spe<00:16:26.959> specifically<00:16:27.560> the 00:16:27.749 --> 00:16:27.759 align:start position:0% we support in spe specifically the 00:16:27.759 --> 00:16:31.389 align:start position:0% we support in spe specifically the component<00:16:28.319> spec<00:16:29.040> and<00:16:29.319> WID<00:16:30.240> so<00:16:30.519> for<00:16:30.759> those<00:16:31.040> who 00:16:31.389 --> 00:16:31.399 align:start position:0% component spec and WID so for those who 00:16:31.399 --> 00:16:34.110 align:start position:0% component spec and WID so for those who know<00:16:31.680> what<00:16:31.839> that<00:16:32.000> means<00:16:32.720> this<00:16:32.880> means<00:16:33.240> that<00:16:33.959> uh 00:16:34.110 --> 00:16:34.120 align:start position:0% know what that means this means that uh 00:16:34.120 --> 00:16:35.870 align:start position:0% know what that means this means that uh all<00:16:34.279> of<00:16:34.440> this<00:16:34.639> technology<00:16:35.120> works<00:16:35.360> in<00:16:35.480> the 00:16:35.870 --> 00:16:35.880 align:start position:0% all of this technology works in the 00:16:35.880 --> 00:16:38.230 align:start position:0% all of this technology works in the browser<00:16:36.880> it's<00:16:37.079> also<00:16:37.319> available<00:16:37.720> as<00:16:37.839> a<00:16:37.920> rust 00:16:38.230 --> 00:16:38.240 align:start position:0% browser it's also available as a rust 00:16:38.240 --> 00:16:41.110 align:start position:0% browser it's also available as a rust API<00:16:38.839> or<00:16:39.440> uh<00:16:39.600> as<00:16:39.800> typescript<00:16:40.639> which<00:16:40.800> is<00:16:40.920> our 00:16:41.110 --> 00:16:41.120 align:start position:0% API or uh as typescript which is our 00:16:41.120 --> 00:16:44.030 align:start position:0% API or uh as typescript which is our first<00:16:41.399> Target<00:16:41.800> because<00:16:42.000> most<00:16:42.319> people<00:16:43.319> uh<00:16:43.880> are 00:16:44.030 --> 00:16:44.040 align:start position:0% first Target because most people uh are 00:16:44.040 --> 00:16:48.430 align:start position:0% first Target because most people uh are using 00:16:48.430 --> 00:16:48.440 align:start position:0% 00:16:48.440 --> 00:16:50.790 align:start position:0% typescript<00:16:49.440> so<00:16:49.759> some<00:16:49.880> more<00:16:50.079> applications 00:16:50.790 --> 00:16:50.800 align:start position:0% typescript so some more applications 00:16:50.800 --> 00:16:52.509 align:start position:0% typescript so some more applications code<00:16:51.079> trans<00:16:51.680> I've<00:16:51.839> already<00:16:52.040> done<00:16:52.279> that 00:16:52.509 --> 00:16:52.519 align:start position:0% code trans I've already done that 00:16:52.519 --> 00:16:55.430 align:start position:0% code trans I've already done that documentation<00:16:53.600> generation<00:16:54.600> uh<00:16:54.720> it's<00:16:54.920> easy<00:16:55.199> to 00:16:55.430 --> 00:16:55.440 align:start position:0% documentation generation uh it's easy to 00:16:55.440 --> 00:16:57.269 align:start position:0% documentation generation uh it's easy to generate<00:16:55.839> automatic<00:16:56.319> documents<00:16:57.040> by 00:16:57.269 --> 00:16:57.279 align:start position:0% generate automatic documents by 00:16:57.279 --> 00:16:59.590 align:start position:0% generate automatic documents by extracting<00:16:57.759> function<00:16:58.160> signatures<00:16:59.279> doing 00:16:59.590 --> 00:16:59.600 align:start position:0% extracting function signatures doing 00:16:59.600 --> 00:17:02.870 align:start position:0% extracting function signatures doing structure<00:17:00.560> analysis<00:17:01.560> um<00:17:02.120> checking<00:17:02.480> for 00:17:02.870 --> 00:17:02.880 align:start position:0% structure analysis um checking for 00:17:02.880 --> 00:17:04.470 align:start position:0% structure analysis um checking for particular<00:17:03.279> usage<00:17:03.720> patterns<00:17:04.240> and 00:17:04.470 --> 00:17:04.480 align:start position:0% particular usage patterns and 00:17:04.480 --> 00:17:06.510 align:start position:0% particular usage patterns and documenting<00:17:05.000> them<00:17:05.480> and<00:17:05.679> processing<00:17:06.120> comments 00:17:06.510 --> 00:17:06.520 align:start position:0% documenting them and processing comments 00:17:06.520 --> 00:17:08.710 align:start position:0% documenting them and processing comments as<00:17:06.640> I<00:17:06.720> mentioned<00:17:07.079> before<00:17:07.360> you<00:17:07.480> might<00:17:07.760> have 00:17:08.710 --> 00:17:08.720 align:start position:0% as I mentioned before you might have 00:17:08.720 --> 00:17:11.350 align:start position:0% as I mentioned before you might have validation<00:17:09.720> uh<00:17:10.120> information<00:17:10.600> in<00:17:10.760> a<00:17:10.919> certain 00:17:11.350 --> 00:17:11.360 align:start position:0% validation uh information in a certain 00:17:11.360 --> 00:17:14.309 align:start position:0% validation uh information in a certain specialized<00:17:12.000> Contex<00:17:12.600> uh<00:17:12.880> comment<00:17:13.240> format<00:17:14.199> now 00:17:14.309 --> 00:17:14.319 align:start position:0% specialized Contex uh comment format now 00:17:14.319 --> 00:17:15.789 align:start position:0% specialized Contex uh comment format now you<00:17:14.400> can<00:17:14.559> also<00:17:14.880> use<00:17:15.039> this<00:17:15.240> technology<00:17:15.640> in 00:17:15.789 --> 00:17:15.799 align:start position:0% you can also use this technology in 00:17:15.799 --> 00:17:18.270 align:start position:0% you can also use this technology in combination<00:17:16.360> with<00:17:16.919> AI<00:17:17.280> tooling<00:17:17.679> for<00:17:17.880> example 00:17:18.270 --> 00:17:18.280 align:start position:0% combination with AI tooling for example 00:17:18.280 --> 00:17:21.870 align:start position:0% combination with AI tooling for example to<00:17:18.679> produce<00:17:19.679> uh<00:17:19.880> diagrams<00:17:20.720> from<00:17:20.959> your<00:17:21.160> code 00:17:21.870 --> 00:17:21.880 align:start position:0% to produce uh diagrams from your code 00:17:21.880 --> 00:17:24.949 align:start position:0% to produce uh diagrams from your code you<00:17:22.000> can<00:17:22.160> use<00:17:22.360> this<00:17:22.600> with<00:17:23.199> uh<00:17:23.360> by<00:17:23.839> encoding<00:17:24.839> uh 00:17:24.949 --> 00:17:24.959 align:start position:0% you can use this with uh by encoding uh 00:17:24.959 --> 00:17:27.830 align:start position:0% you can use this with uh by encoding uh the<00:17:25.039> slang<00:17:25.559> API<00:17:26.160> as<00:17:26.280> a 00:17:27.830 --> 00:17:27.840 align:start position:0% the slang API as a 00:17:27.840 --> 00:17:30.390 align:start position:0% the slang API as a rag<00:17:28.919> so<00:17:29.160> what<00:17:29.280> are<00:17:29.400> the<00:17:29.520> key<00:17:29.720> benefits<00:17:30.160> well 00:17:30.390 --> 00:17:30.400 align:start position:0% rag so what are the key benefits well 00:17:30.400 --> 00:17:32.710 align:start position:0% rag so what are the key benefits well structure<00:17:30.799> aware<00:17:31.160> queries<00:17:32.080> your<00:17:32.280> queries 00:17:32.710 --> 00:17:32.720 align:start position:0% structure aware queries your queries 00:17:32.720 --> 00:17:34.390 align:start position:0% structure aware queries your queries naturally<00:17:33.200> align<00:17:33.520> with<00:17:33.640> a<00:17:33.760> structure<00:17:34.080> of<00:17:34.200> the 00:17:34.390 --> 00:17:34.400 align:start position:0% naturally align with a structure of the 00:17:34.400 --> 00:17:36.029 align:start position:0% naturally align with a structure of the code<00:17:34.640> that<00:17:34.760> you're<00:17:34.880> trying<00:17:35.039> to<00:17:35.200> match<00:17:35.880> you 00:17:36.029 --> 00:17:36.039 align:start position:0% code that you're trying to match you 00:17:36.039 --> 00:17:37.270 align:start position:0% code that you're trying to match you don't<00:17:36.200> have<00:17:36.320> to<00:17:36.400> think<00:17:36.559> about<00:17:36.880> trees<00:17:37.080> and 00:17:37.270 --> 00:17:37.280 align:start position:0% don't have to think about trees and 00:17:37.280 --> 00:17:39.830 align:start position:0% don't have to think about trees and nodes<00:17:37.720> and<00:17:38.559> and<00:17:38.880> uh 00:17:39.830 --> 00:17:39.840 align:start position:0% nodes and and uh 00:17:39.840 --> 00:17:42.630 align:start position:0% nodes and and uh traversal<00:17:40.840> uh<00:17:41.160> complete<00:17:41.520> syntax 00:17:42.630 --> 00:17:42.640 align:start position:0% traversal uh complete syntax 00:17:42.640 --> 00:17:45.070 align:start position:0% traversal uh complete syntax preservation<00:17:43.640> you<00:17:43.840> never<00:17:44.039> lose 00:17:45.070 --> 00:17:45.080 align:start position:0% preservation you never lose 00:17:45.080 --> 00:17:47.150 align:start position:0% preservation you never lose information<00:17:46.080> perform<00:17:46.440> Transformations 00:17:47.150 --> 00:17:47.160 align:start position:0% information perform Transformations 00:17:47.160 --> 00:17:49.270 align:start position:0% information perform Transformations without<00:17:47.400> losing<00:17:47.679> the<00:17:47.919> formatting<00:17:48.919> and<00:17:49.120> you 00:17:49.270 --> 00:17:49.280 align:start position:0% without losing the formatting and you 00:17:49.280 --> 00:17:51.990 align:start position:0% without losing the formatting and you can<00:17:49.720> round<00:17:50.360> trip<00:17:51.120> from<00:17:51.320> a 00:17:51.990 --> 00:17:52.000 align:start position:0% can round trip from a 00:17:52.000 --> 00:17:54.149 align:start position:0% can round trip from a CST<00:17:53.000> uh<00:17:53.160> back<00:17:53.280> to 00:17:54.149 --> 00:17:54.159 align:start position:0% CST uh back to 00:17:54.159 --> 00:17:56.950 align:start position:0% CST uh back to Source<00:17:55.159> efficient<00:17:55.559> patent<00:17:55.840> matching<00:17:56.240> so<00:17:56.640> we 00:17:56.950 --> 00:17:56.960 align:start position:0% Source efficient patent matching so we 00:17:56.960 --> 00:17:58.870 align:start position:0% Source efficient patent matching so we can<00:17:57.200> spend<00:17:57.679> all<00:17:57.840> the<00:17:57.960> effort<00:17:58.280> required<00:17:58.600> to 00:17:58.870 --> 00:17:58.880 align:start position:0% can spend all the effort required to 00:17:58.880 --> 00:18:00.750 align:start position:0% can spend all the effort required to make<00:17:59.039> this<00:17:59.240> efficient<00:18:00.039> if<00:18:00.159> you<00:18:00.240> know<00:18:00.440> anything 00:18:00.750 --> 00:18:00.760 align:start position:0% make this efficient if you know anything 00:18:00.760 --> 00:18:03.029 align:start position:0% make this efficient if you know anything about<00:18:01.440> the<00:18:01.600> state-of-the-art<00:18:02.360> in<00:18:02.520> terms<00:18:02.799> of 00:18:03.029 --> 00:18:03.039 align:start position:0% about the state-of-the-art in terms of 00:18:03.039 --> 00:18:05.110 align:start position:0% about the state-of-the-art in terms of tree<00:18:03.440> pattern<00:18:03.799> matching<00:18:04.480> and<00:18:04.640> in<00:18:04.760> fact<00:18:04.960> we're 00:18:05.110 --> 00:18:05.120 align:start position:0% tree pattern matching and in fact we're 00:18:05.120 --> 00:18:08.510 align:start position:0% tree pattern matching and in fact we're not<00:18:05.400> a<00:18:06.039> a<00:18:06.200> search<00:18:06.520> engine<00:18:06.919> we<00:18:07.039> are<00:18:07.200> a<00:18:07.520> unifier 00:18:08.510 --> 00:18:08.520 align:start position:0% not a a search engine we are a unifier 00:18:08.520 --> 00:18:12.510 align:start position:0% not a a search engine we are a unifier so<00:18:08.760> we<00:18:08.919> use<00:18:09.120> a<00:18:09.640> prolog<00:18:10.640> datalog<00:18:11.559> based<00:18:12.360> uh 00:18:12.510 --> 00:18:12.520 align:start position:0% so we use a prolog datalog based uh 00:18:12.520 --> 00:18:14.230 align:start position:0% so we use a prolog datalog based uh mechanism<00:18:13.000> which<00:18:13.320> returns<00:18:13.520> you<00:18:13.760> all<00:18:14.000> the 00:18:14.230 --> 00:18:14.240 align:start position:0% mechanism which returns you all the 00:18:14.240 --> 00:18:16.310 align:start position:0% mechanism which returns you all the potential<00:18:14.600> matching<00:18:15.080> results<00:18:15.720> not<00:18:15.960> just<00:18:16.120> the 00:18:16.310 --> 00:18:16.320 align:start position:0% potential matching results not just the 00:18:16.320 --> 00:18:18.870 align:start position:0% potential matching results not just the first<00:18:16.600> one<00:18:17.600> you<00:18:17.720> can<00:18:17.919> avoid<00:18:18.240> unnecessary 00:18:18.870 --> 00:18:18.880 align:start position:0% first one you can avoid unnecessary 00:18:18.880 --> 00:18:20.789 align:start position:0% first one you can avoid unnecessary traversals<00:18:19.480> we<00:18:19.600> can<00:18:19.760> case<00:18:20.120> results<00:18:20.520> we<00:18:20.640> can 00:18:20.789 --> 00:18:20.799 align:start position:0% traversals we can case results we can 00:18:20.799 --> 00:18:23.270 align:start position:0% traversals we can case results we can index<00:18:21.200> the<00:18:21.320> syntax<00:18:21.799> tree<00:18:22.600> make<00:18:22.880> it<00:18:23.039> very 00:18:23.270 --> 00:18:23.280 align:start position:0% index the syntax tree make it very 00:18:23.280 --> 00:18:25.149 align:start position:0% index the syntax tree make it very efficient<00:18:23.679> it<00:18:23.799> would<00:18:23.960> take<00:18:24.120> a<00:18:24.280> lot<00:18:24.400> of<00:18:24.600> effort 00:18:25.149 --> 00:18:25.159 align:start position:0% efficient it would take a lot of effort 00:18:25.159 --> 00:18:27.750 align:start position:0% efficient it would take a lot of effort to<00:18:25.520> uh<00:18:25.640> get<00:18:25.799> the<00:18:26.000> same<00:18:26.960> uh<00:18:27.120> result<00:18:27.440> if<00:18:27.559> you 00:18:27.750 --> 00:18:27.760 align:start position:0% to uh get the same uh result if you 00:18:27.760 --> 00:18:29.789 align:start position:0% to uh get the same uh result if you doing<00:18:27.960> it<00:18:28.080> yourself 00:18:29.789 --> 00:18:29.799 align:start position:0% doing it yourself 00:18:29.799 --> 00:18:32.270 align:start position:0% doing it yourself composable<00:18:30.360> syntax<00:18:30.799> rules<00:18:31.640> you<00:18:31.760> can<00:18:31.960> combine 00:18:32.270 --> 00:18:32.280 align:start position:0% composable syntax rules you can combine 00:18:32.280 --> 00:18:33.789 align:start position:0% composable syntax rules you can combine simple<00:18:32.600> rules<00:18:32.880> to<00:18:32.960> make<00:18:33.159> bigger<00:18:33.400> ones<00:18:33.600> you<00:18:33.679> can 00:18:33.789 --> 00:18:33.799 align:start position:0% simple rules to make bigger ones you can 00:18:33.799 --> 00:18:37.110 align:start position:0% simple rules to make bigger ones you can have<00:18:33.919> a<00:18:34.039> big<00:18:34.280> library<00:18:35.159> of<00:18:35.400> these<00:18:36.039> uh<00:18:36.240> pattern 00:18:37.110 --> 00:18:37.120 align:start position:0% have a big library of these uh pattern 00:18:37.120 --> 00:18:40.310 align:start position:0% have a big library of these uh pattern and<00:18:37.240> you<00:18:37.360> can<00:18:37.520> reuse<00:18:38.039> them<00:18:38.640> uh<00:18:38.799> over<00:18:39.039> your<00:18:39.320> code 00:18:40.310 --> 00:18:40.320 align:start position:0% and you can reuse them uh over your code 00:18:40.320 --> 00:18:42.669 align:start position:0% and you can reuse them uh over your code share<00:18:40.679> queries<00:18:41.120> between<00:18:41.440> your 00:18:42.669 --> 00:18:42.679 align:start position:0% share queries between your 00:18:42.679 --> 00:18:44.870 align:start position:0% share queries between your projects<00:18:43.679> you've<00:18:43.880> got<00:18:44.039> maintainable 00:18:44.870 --> 00:18:44.880 align:start position:0% projects you've got maintainable 00:18:44.880 --> 00:18:47.549 align:start position:0% projects you've got maintainable analysis<00:18:45.440> code<00:18:46.159> so<00:18:46.400> the<00:18:46.520> queries<00:18:47.159> express 00:18:47.549 --> 00:18:47.559 align:start position:0% analysis code so the queries express 00:18:47.559 --> 00:18:49.909 align:start position:0% analysis code so the queries express your<00:18:47.760> intent<00:18:48.480> not<00:18:48.760> how<00:18:48.960> you<00:18:49.440> not<00:18:49.640> what<00:18:49.799> you 00:18:49.909 --> 00:18:49.919 align:start position:0% your intent not how you not what you 00:18:49.919 --> 00:18:51.870 align:start position:0% your intent not how you not what you want<00:18:50.080> to<00:18:50.240> do<00:18:50.600> uh<00:18:50.720> how<00:18:50.880> you<00:18:50.960> want<00:18:51.080> to<00:18:51.240> do<00:18:51.360> it<00:18:51.679> but 00:18:51.870 --> 00:18:51.880 align:start position:0% want to do uh how you want to do it but 00:18:51.880 --> 00:18:53.830 align:start position:0% want to do uh how you want to do it but what<00:18:52.000> you<00:18:52.120> want<00:18:52.240> to<00:18:52.400> do<00:18:52.880> your<00:18:53.039> code<00:18:53.320> is<00:18:53.440> shorter 00:18:53.830 --> 00:18:53.840 align:start position:0% what you want to do your code is shorter 00:18:53.840 --> 00:18:56.310 align:start position:0% what you want to do your code is shorter it's<00:18:54.000> easier<00:18:54.320> to<00:18:54.799> understand<00:18:55.559> any<00:18:55.799> changes<00:18:56.159> to 00:18:56.310 --> 00:18:56.320 align:start position:0% it's easier to understand any changes to 00:18:56.320 --> 00:18:58.950 align:start position:0% it's easier to understand any changes to the<00:18:56.480> language<00:18:57.400> we<00:18:57.600> say<00:18:57.880> ter<00:18:58.200> that<00:18:58.320> slang<00:18:58.760> takes 00:18:58.950 --> 00:18:58.960 align:start position:0% the language we say ter that slang takes 00:18:58.960 --> 00:19:00.669 align:start position:0% the language we say ter that slang takes care<00:18:59.120> of<00:18:59.240> that<00:18:59.360> so<00:18:59.480> you<00:18:59.559> don't<00:18:59.799> have<00:18:59.919> to<00:19:00.440> less 00:19:00.669 --> 00:19:00.679 align:start position:0% care of that so you don't have to less 00:19:00.679 --> 00:19:03.430 align:start position:0% care of that so you don't have to less code<00:19:01.039> means<00:19:01.360> fewer<00:19:01.799> bugs<00:19:02.520> and<00:19:02.679> these<00:19:02.919> benefits 00:19:03.430 --> 00:19:03.440 align:start position:0% code means fewer bugs and these benefits 00:19:03.440 --> 00:19:06.549 align:start position:0% code means fewer bugs and these benefits compound<00:19:04.200> it's<00:19:04.360> not<00:19:04.559> 1+<00:19:05.080> 1+<00:19:05.600> one<00:19:05.919> it's<00:19:06.440> you 00:19:06.549 --> 00:19:06.559 align:start position:0% compound it's not 1+ 1+ one it's you 00:19:06.559 --> 00:19:09.230 align:start position:0% compound it's not 1+ 1+ one it's you know<00:19:07.000> far<00:19:07.360> this<00:19:07.720> the<00:19:08.080> uh<00:19:08.440> whole<00:19:08.840> is<00:19:09.039> far 00:19:09.230 --> 00:19:09.240 align:start position:0% know far this the uh whole is far 00:19:09.240 --> 00:19:13.470 align:start position:0% know far this the uh whole is far greater<00:19:09.520> than<00:19:09.640> the<00:19:09.720> sum<00:19:09.880> of<00:19:10.000> the 00:19:13.470 --> 00:19:13.480 align:start position:0% 00:19:13.480 --> 00:19:16.230 align:start position:0% parts<00:19:14.480> so<00:19:15.200> what<00:19:15.400> impact<00:19:15.679> does<00:19:15.840> this<00:19:16.000> have<00:19:16.120> on 00:19:16.230 --> 00:19:16.240 align:start position:0% parts so what impact does this have on 00:19:16.240 --> 00:19:18.630 align:start position:0% parts so what impact does this have on your<00:19:16.360> development<00:19:16.840> well<00:19:17.159> before<00:19:18.159> using<00:19:18.480> this 00:19:18.630 --> 00:19:18.640 align:start position:0% your development well before using this 00:19:18.640 --> 00:19:21.390 align:start position:0% your development well before using this query<00:19:19.200> API<00:19:20.200> it<00:19:20.400> spend<00:19:20.760> significant<00:19:21.240> time 00:19:21.390 --> 00:19:21.400 align:start position:0% query API it spend significant time 00:19:21.400 --> 00:19:23.870 align:start position:0% query API it spend significant time writing<00:19:21.720> and<00:19:21.840> debugging<00:19:22.280> the<00:19:22.400> traversal<00:19:22.960> code 00:19:23.870 --> 00:19:23.880 align:start position:0% writing and debugging the traversal code 00:19:23.880 --> 00:19:25.710 align:start position:0% writing and debugging the traversal code you'd<00:19:24.159> struggle<00:19:24.600> with<00:19:24.799> maintaining<00:19:25.480> the 00:19:25.710 --> 00:19:25.720 align:start position:0% you'd struggle with maintaining the 00:19:25.720 --> 00:19:28.110 align:start position:0% you'd struggle with maintaining the analysis<00:19:26.320> logic<00:19:27.039> and<00:19:27.159> you'd<00:19:27.400> face<00:19:27.679> challenges 00:19:28.110 --> 00:19:28.120 align:start position:0% analysis logic and you'd face challenges 00:19:28.120 --> 00:19:29.270 align:start position:0% analysis logic and you'd face challenges when<00:19:28.280> adding<00:19:28.480> new 00:19:29.270 --> 00:19:29.280 align:start position:0% when adding new 00:19:29.280 --> 00:19:31.950 align:start position:0% when adding new features<00:19:30.280> after<00:19:30.520> it<00:19:31.039> you<00:19:31.200> end<00:19:31.400> up<00:19:31.520> with<00:19:31.679> clear 00:19:31.950 --> 00:19:31.960 align:start position:0% features after it you end up with clear 00:19:31.960 --> 00:19:34.230 align:start position:0% features after it you end up with clear Focus<00:19:32.400> code<00:19:32.720> it's<00:19:32.880> easy<00:19:33.120> to<00:19:33.280> maintain<00:19:34.080> you've 00:19:34.230 --> 00:19:34.240 align:start position:0% Focus code it's easy to maintain you've 00:19:34.240 --> 00:19:36.070 align:start position:0% Focus code it's easy to maintain you've got<00:19:34.360> a<00:19:34.520> robust<00:19:34.960> implementation<00:19:35.640> and<00:19:35.799> it's 00:19:36.070 --> 00:19:36.080 align:start position:0% got a robust implementation and it's 00:19:36.080 --> 00:19:37.750 align:start position:0% got a robust implementation and it's highly 00:19:37.750 --> 00:19:37.760 align:start position:0% highly 00:19:37.760 --> 00:19:44.390 align:start position:0% highly extensible<00:19:38.760> and<00:19:39.240> that<00:19:39.400> is<00:19:39.559> it<00:19:40.320> any 00:19:44.390 --> 00:19:44.400 align:start position:0% 00:19:44.400 --> 00:19:47.630 align:start position:0% questions<00:19:45.679> fantastic<00:19:46.679> thank<00:19:46.840> you<00:19:47.000> Anthony 00:19:47.630 --> 00:19:47.640 align:start position:0% questions fantastic thank you Anthony 00:19:47.640 --> 00:19:49.950 align:start position:0% questions fantastic thank you Anthony all<00:19:47.760> right<00:19:47.919> let's<00:19:48.120> get<00:19:48.320> with<00:19:48.600> the<00:19:49.559> let's<00:19:49.760> get 00:19:49.950 --> 00:19:49.960 align:start position:0% all right let's get with the let's get 00:19:49.960 --> 00:19:53.190 align:start position:0% all right let's get with the let's get with<00:19:50.120> the<00:19:50.320> questions<00:19:51.320> so<00:19:52.159> folks<00:19:52.559> remember<00:19:53.080> you 00:19:53.190 --> 00:19:53.200 align:start position:0% with the questions so folks remember you 00:19:53.200 --> 00:19:55.710 align:start position:0% with the questions so folks remember you can<00:19:53.320> scan<00:19:53.640> that<00:19:53.799> QR<00:19:54.159> code<00:19:54.720> add<00:19:55.120> questions<00:19:55.480> to 00:19:55.710 --> 00:19:55.720 align:start position:0% can scan that QR code add questions to 00:19:55.720 --> 00:19:58.230 align:start position:0% can scan that QR code add questions to that<00:19:55.919> list<00:19:56.400> smash<00:19:56.840> that<00:19:57.159> up<00:19:57.360> vote<00:19:57.600> button<00:19:58.039> that 00:19:58.230 --> 00:19:58.240 align:start position:0% that list smash that up vote button that 00:19:58.240 --> 00:20:01.270 align:start position:0% that list smash that up vote button that the<00:19:58.360> most<00:19:58.799> interesting<00:19:59.159> question<00:19:59.559> gets<00:20:00.280> asked 00:20:01.270 --> 00:20:01.280 align:start position:0% the most interesting question gets asked 00:20:01.280 --> 00:20:03.950 align:start position:0% the most interesting question gets asked let's<00:20:01.520> go<00:20:01.679> with<00:20:01.799> the<00:20:01.960> first<00:20:02.240> one<00:20:03.240> what<00:20:03.360> are 00:20:03.950 --> 00:20:03.960 align:start position:0% let's go with the first one what are 00:20:03.960 --> 00:20:06.950 align:start position:0% let's go with the first one what are advantages<00:20:04.960> to<00:20:05.159> using<00:20:05.480> slang<00:20:06.120> compared<00:20:06.440> to 00:20:06.950 --> 00:20:06.960 align:start position:0% advantages to using slang compared to 00:20:06.960 --> 00:20:09.470 align:start position:0% advantages to using slang compared to srep<00:20:07.960> uh<00:20:08.080> well<00:20:08.200> I<00:20:08.320> must<00:20:08.520> admit<00:20:08.799> I'm<00:20:08.919> not 00:20:09.470 --> 00:20:09.480 align:start position:0% srep uh well I must admit I'm not 00:20:09.480 --> 00:20:12.070 align:start position:0% srep uh well I must admit I'm not familiar<00:20:10.000> with<00:20:10.799> uh<00:20:10.960> srep<00:20:11.559> but<00:20:11.640> I<00:20:11.720> know<00:20:11.919> the 00:20:12.070 --> 00:20:12.080 align:start position:0% familiar with uh srep but I know the 00:20:12.080 --> 00:20:14.669 align:start position:0% familiar with uh srep but I know the general<00:20:12.799> uh<00:20:13.000> concept<00:20:13.880> the<00:20:14.080> specific<00:20:14.440> thing 00:20:14.669 --> 00:20:14.679 align:start position:0% general uh concept the specific thing 00:20:14.679 --> 00:20:16.270 align:start position:0% general uh concept the specific thing here<00:20:14.799> that<00:20:14.960> this<00:20:15.039> is<00:20:15.120> a<00:20:15.320> programmatic<00:20:15.919> tool 00:20:16.270 --> 00:20:16.280 align:start position:0% here that this is a programmatic tool 00:20:16.280 --> 00:20:18.710 align:start position:0% here that this is a programmatic tool that<00:20:16.400> you<00:20:16.559> use<00:20:16.799> to<00:20:16.960> build<00:20:17.240> other<00:20:17.480> tools<00:20:18.400> now<00:20:18.559> of 00:20:18.710 --> 00:20:18.720 align:start position:0% that you use to build other tools now of 00:20:18.720 --> 00:20:20.630 align:start position:0% that you use to build other tools now of course<00:20:18.880> you<00:20:19.000> can<00:20:19.200> combine<00:20:19.640> things<00:20:19.880> like 00:20:20.630 --> 00:20:20.640 align:start position:0% course you can combine things like 00:20:20.640 --> 00:20:24.549 align:start position:0% course you can combine things like srep<00:20:21.640> uh<00:20:21.960> I<00:20:22.360> imagine<00:20:23.360> uh<00:20:23.520> but<00:20:23.720> I<00:20:23.799> don't<00:20:24.039> know<00:20:24.360> if 00:20:24.549 --> 00:20:24.559 align:start position:0% srep uh I imagine uh but I don't know if 00:20:24.559 --> 00:20:26.350 align:start position:0% srep uh I imagine uh but I don't know if that<00:20:24.679> is<00:20:24.840> something<00:20:25.159> that<00:20:25.280> you<00:20:25.400> would<00:20:25.760> include 00:20:26.350 --> 00:20:26.360 align:start position:0% that is something that you would include 00:20:26.360 --> 00:20:29.549 align:start position:0% that is something that you would include in<00:20:26.520> a<00:20:26.679> tool<00:20:27.400> for<00:20:27.880> analyzing<00:20:29.120> lots<00:20:29.320> of 00:20:29.549 --> 00:20:29.559 align:start position:0% in a tool for analyzing lots of 00:20:29.559 --> 00:20:31.789 align:start position:0% in a tool for analyzing lots of different<00:20:29.880> versions<00:20:30.320> of<00:20:30.640> solidity<00:20:31.640> that 00:20:31.789 --> 00:20:31.799 align:start position:0% different versions of solidity that 00:20:31.799 --> 00:20:34.149 align:start position:0% different versions of solidity that makes<00:20:32.039> sense<00:20:32.360> thank<00:20:32.520> you<00:20:33.360> how<00:20:33.559> does<00:20:33.760> slang 00:20:34.149 --> 00:20:34.159 align:start position:0% makes sense thank you how does slang 00:20:34.159 --> 00:20:36.909 align:start position:0% makes sense thank you how does slang differ<00:20:34.600> from<00:20:34.760> a<00:20:35.000> fine-tuned<00:20:35.960> llm<00:20:36.760> could 00:20:36.909 --> 00:20:36.919 align:start position:0% differ from a fine-tuned llm could 00:20:36.919 --> 00:20:39.630 align:start position:0% differ from a fine-tuned llm could slang's<00:20:37.280> modularity<00:20:38.159> allow<00:20:38.480> to<00:20:38.640> use<00:20:38.880> llms<00:20:39.520> in 00:20:39.630 --> 00:20:39.640 align:start position:0% slang's modularity allow to use llms in 00:20:39.640 --> 00:20:42.310 align:start position:0% slang's modularity allow to use llms in the<00:20:39.760> future<00:20:40.480> oh<00:20:40.720> this<00:20:40.840> is<00:20:41.280> I'm<00:20:41.400> in<00:20:41.559> applied 00:20:42.310 --> 00:20:42.320 align:start position:0% the future oh this is I'm in applied 00:20:42.320 --> 00:20:45.270 align:start position:0% the future oh this is I'm in applied research<00:20:43.320> and<00:20:43.919> uh<00:20:44.120> this<00:20:44.240> is<00:20:44.400> something<00:20:44.960> that 00:20:45.270 --> 00:20:45.280 align:start position:0% research and uh this is something that 00:20:45.280 --> 00:20:48.470 align:start position:0% research and uh this is something that is<00:20:45.840> very<00:20:46.200> actively<00:20:46.640> under<00:20:47.200> research<00:20:48.200> I'm<00:20:48.320> not 00:20:48.470 --> 00:20:48.480 align:start position:0% is very actively under research I'm not 00:20:48.480 --> 00:20:52.710 align:start position:0% is very actively under research I'm not making<00:20:48.799> any<00:20:49.440> commitment<00:20:50.440> uh<00:20:51.320> but<00:20:52.320> if<00:20:52.440> you've 00:20:52.710 --> 00:20:52.720 align:start position:0% making any commitment uh but if you've 00:20:52.720 --> 00:20:55.870 align:start position:0% making any commitment uh but if you've used<00:20:53.080> fine-tuned<00:20:53.880> llms<00:20:54.880> uh<00:20:55.159> and<00:20:55.480> I've<00:20:55.640> used 00:20:55.870 --> 00:20:55.880 align:start position:0% used fine-tuned llms uh and I've used 00:20:55.880 --> 00:20:57.590 align:start position:0% used fine-tuned llms uh and I've used them<00:20:56.039> a<00:20:56.159> lot<00:20:56.320> for<00:20:56.480> example<00:20:56.919> a<00:20:57.000> lot<00:20:57.120> of<00:20:57.240> the<00:20:57.360> code 00:20:57.590 --> 00:20:57.600 align:start position:0% them a lot for example a lot of the code 00:20:57.600 --> 00:20:59.789 align:start position:0% them a lot for example a lot of the code that<00:20:57.720> I<00:20:57.880> write<00:20:58.600> is<00:20:58.760> actually<00:20:59.039> written<00:20:59.360> by 00:20:59.789 --> 00:20:59.799 align:start position:0% that I write is actually written by 00:20:59.799 --> 00:21:02.669 align:start position:0% that I write is actually written by Claude<00:21:00.799> uh<00:21:00.960> a<00:21:01.080> lot<00:21:01.200> of<00:21:01.320> this<00:21:01.520> presentation<00:21:02.520> was 00:21:02.669 --> 00:21:02.679 align:start position:0% Claude uh a lot of this presentation was 00:21:02.679 --> 00:21:06.669 align:start position:0% Claude uh a lot of this presentation was written<00:21:03.000> by<00:21:03.280> Claude<00:21:04.280> um<00:21:05.000> amazing<00:21:05.520> tool<00:21:05.960> but 00:21:06.669 --> 00:21:06.679 align:start position:0% written by Claude um amazing tool but 00:21:06.679 --> 00:21:08.750 align:start position:0% written by Claude um amazing tool but you<00:21:06.840> always<00:21:07.080> need<00:21:07.240> a<00:21:07.400> human<00:21:07.640> in<00:21:07.799> the<00:21:07.919> loop<00:21:08.480> so 00:21:08.750 --> 00:21:08.760 align:start position:0% you always need a human in the loop so 00:21:08.760 --> 00:21:12.149 align:start position:0% you always need a human in the loop so yes<00:21:08.919> you<00:21:09.080> can<00:21:09.280> do<00:21:09.559> this<00:21:10.200> uh<00:21:10.559> using<00:21:11.000> llms<00:21:11.640> but 00:21:12.149 --> 00:21:12.159 align:start position:0% yes you can do this uh using llms but 00:21:12.159 --> 00:21:14.070 align:start position:0% yes you can do this uh using llms but the<00:21:12.279> thing<00:21:12.440> with<00:21:12.600> llms<00:21:13.159> is<00:21:13.279> that<00:21:13.480> they<00:21:13.640> are<00:21:13.919> a 00:21:14.070 --> 00:21:14.080 align:start position:0% the thing with llms is that they are a 00:21:14.080 --> 00:21:16.549 align:start position:0% the thing with llms is that they are a human<00:21:14.320> augmentation<00:21:15.039> tool<00:21:15.840> whereas<00:21:16.400> the 00:21:16.549 --> 00:21:16.559 align:start position:0% human augmentation tool whereas the 00:21:16.559 --> 00:21:17.750 align:start position:0% human augmentation tool whereas the approach<00:21:16.880> that<00:21:17.000> we're<00:21:17.159> talking<00:21:17.360> about<00:21:17.600> here 00:21:17.750 --> 00:21:17.760 align:start position:0% approach that we're talking about here 00:21:17.760 --> 00:21:20.950 align:start position:0% approach that we're talking about here is<00:21:18.000> exact<00:21:18.480> and<00:21:18.880> precise<00:21:19.880> if<00:21:20.000> you've<00:21:20.159> used<00:21:20.480> llms 00:21:20.950 --> 00:21:20.960 align:start position:0% is exact and precise if you've used llms 00:21:20.960 --> 00:21:23.870 align:start position:0% is exact and precise if you've used llms to<00:21:21.120> do<00:21:21.320> this<00:21:21.480> you<00:21:21.640> know<00:21:21.960> that<00:21:22.799> you<00:21:23.279> you<00:21:23.480> spend<00:21:23.760> a 00:21:23.870 --> 00:21:23.880 align:start position:0% to do this you know that you you spend a 00:21:23.880 --> 00:21:25.789 align:start position:0% to do this you know that you you spend a lot<00:21:24.000> of<00:21:24.120> time<00:21:24.279> on<00:21:24.440> prompt<00:21:24.760> engineering<00:21:25.679> and 00:21:25.789 --> 00:21:25.799 align:start position:0% lot of time on prompt engineering and 00:21:25.799 --> 00:21:27.350 align:start position:0% lot of time on prompt engineering and then<00:21:25.919> you<00:21:26.080> cross<00:21:26.320> your<00:21:26.440> fingers<00:21:27.200> and 00:21:27.350 --> 00:21:27.360 align:start position:0% then you cross your fingers and 00:21:27.360 --> 00:21:29.110 align:start position:0% then you cross your fingers and something<00:21:27.679> comes<00:21:28.039> back<00:21:28.600> and<00:21:28.679> it<00:21:28.799> doesn't 00:21:29.110 --> 00:21:29.120 align:start position:0% something comes back and it doesn't 00:21:29.120 --> 00:21:31.149 align:start position:0% something comes back and it doesn't quite<00:21:29.360> work<00:21:29.799> and<00:21:29.919> you<00:21:30.120> prompt<00:21:30.400> it<00:21:30.600> again<00:21:31.000> and 00:21:31.149 --> 00:21:31.159 align:start position:0% quite work and you prompt it again and 00:21:31.159 --> 00:21:34.590 align:start position:0% quite work and you prompt it again and so<00:21:31.320> on<00:21:31.480> and<00:21:31.600> so<00:21:31.799> forth<00:21:32.559> so<00:21:33.559> yes<00:21:34.279> this<00:21:34.440> is 00:21:34.590 --> 00:21:34.600 align:start position:0% so on and so forth so yes this is 00:21:34.600 --> 00:21:36.310 align:start position:0% so on and so forth so yes this is certainly<00:21:35.039> something<00:21:35.520> that<00:21:35.840> uh<00:21:36.000> could<00:21:36.159> be 00:21:36.310 --> 00:21:36.320 align:start position:0% certainly something that uh could be 00:21:36.320 --> 00:21:38.789 align:start position:0% certainly something that uh could be included<00:21:36.760> in<00:21:36.880> the<00:21:37.000> future<00:21:37.720> there's<00:21:37.919> a<00:21:38.159> chance 00:21:38.789 --> 00:21:38.799 align:start position:0% included in the future there's a chance 00:21:38.799 --> 00:21:41.190 align:start position:0% included in the future there's a chance but<00:21:39.200> maybe<00:21:39.480> not<00:21:39.760> now<00:21:40.360> I<00:21:40.440> mean<00:21:40.600> not<00:21:40.760> immediately 00:21:41.190 --> 00:21:41.200 align:start position:0% but maybe not now I mean not immediately 00:21:41.200 --> 00:21:43.590 align:start position:0% but maybe not now I mean not immediately certainly<00:21:41.559> not<00:21:41.799> now<00:21:42.400> okay<00:21:43.240> are<00:21:43.440> the 00:21:43.590 --> 00:21:43.600 align:start position:0% certainly not now okay are the 00:21:43.600 --> 00:21:45.630 align:start position:0% certainly not now okay are the limitations<00:21:44.240> of<00:21:44.400> an<00:21:44.600> of<00:21:44.760> a<00:21:44.880> tree<00:21:45.200> visitor 00:21:45.630 --> 00:21:45.640 align:start position:0% limitations of an of a tree visitor 00:21:45.640 --> 00:21:47.750 align:start position:0% limitations of an of a tree visitor based<00:21:46.039> approach<00:21:46.520> not<00:21:46.760> solved<00:21:47.200> by<00:21:47.320> using<00:21:47.600> an 00:21:47.750 --> 00:21:47.760 align:start position:0% based approach not solved by using an 00:21:47.760 --> 00:21:49.630 align:start position:0% based approach not solved by using an API<00:21:48.200> with<00:21:48.360> CFG<00:21:48.840> and<00:21:49.039> intermediate 00:21:49.630 --> 00:21:49.640 align:start position:0% API with CFG and intermediate 00:21:49.640 --> 00:21:52.549 align:start position:0% API with CFG and intermediate representation<00:21:50.320> like<00:21:50.520> Slither 00:21:52.549 --> 00:21:52.559 align:start position:0% representation like Slither 00:21:52.559 --> 00:21:54.110 align:start position:0% representation like Slither provides 00:21:54.110 --> 00:21:54.120 align:start position:0% provides 00:21:54.120 --> 00:21:57.470 align:start position:0% provides uh<00:21:55.120> well<00:21:55.400> if<00:21:55.640> if<00:21:55.799> by<00:21:56.039> CFG<00:21:57.039> well<00:21:57.120> you're<00:21:57.279> either 00:21:57.470 --> 00:21:57.480 align:start position:0% uh well if if by CFG well you're either 00:21:57.480 --> 00:21:58.870 align:start position:0% uh well if if by CFG well you're either meaning<00:21:57.799> two<00:21:58.000> things<00:21:58.200> you're<00:21:58.320> either<00:21:58.640> meaning 00:21:58.870 --> 00:21:58.880 align:start position:0% meaning two things you're either meaning 00:21:58.880 --> 00:22:01.190 align:start position:0% meaning two things you're either meaning the<00:21:59.000> control<00:21:59.279> flow<00:21:59.640> graph<00:22:00.600> uh<00:22:00.760> which<00:22:00.919> is 00:22:01.190 --> 00:22:01.200 align:start position:0% the control flow graph uh which is 00:22:01.200 --> 00:22:02.510 align:start position:0% the control flow graph uh which is typically<00:22:01.559> something<00:22:01.840> you'd<00:22:02.039> find<00:22:02.200> in<00:22:02.320> an 00:22:02.510 --> 00:22:02.520 align:start position:0% typically something you'd find in an 00:22:02.520 --> 00:22:05.909 align:start position:0% typically something you'd find in an abstract<00:22:02.960> syntax<00:22:03.520> tree<00:22:04.520> uh<00:22:04.640> or<00:22:04.880> if<00:22:05.000> you<00:22:05.200> mean 00:22:05.909 --> 00:22:05.919 align:start position:0% abstract syntax tree uh or if you mean 00:22:05.919 --> 00:22:07.950 align:start position:0% abstract syntax tree uh or if you mean control<00:22:06.279> flow<00:22:06.760> as<00:22:06.960> exposed<00:22:07.360> by<00:22:07.480> rust<00:22:07.799> for 00:22:07.950 --> 00:22:07.960 align:start position:0% control flow as exposed by rust for 00:22:07.960 --> 00:22:10.230 align:start position:0% control flow as exposed by rust for example<00:22:08.960> uh<00:22:09.159> and<00:22:09.520> this<00:22:09.600> is<00:22:09.760> something<00:22:10.120> where 00:22:10.230 --> 00:22:10.240 align:start position:0% example uh and this is something where 00:22:10.240 --> 00:22:12.590 align:start position:0% example uh and this is something where you<00:22:10.400> reify<00:22:10.960> your<00:22:11.120> control<00:22:11.440> flow<00:22:12.120> so<00:22:12.320> you 00:22:12.590 --> 00:22:12.600 align:start position:0% you reify your control flow so you 00:22:12.600 --> 00:22:13.950 align:start position:0% you reify your control flow so you return<00:22:12.760> a<00:22:12.919> token<00:22:13.200> in<00:22:13.360> your<00:22:13.520> visitor<00:22:13.840> which 00:22:13.950 --> 00:22:13.960 align:start position:0% return a token in your visitor which 00:22:13.960 --> 00:22:15.750 align:start position:0% return a token in your visitor which says<00:22:14.200> do<00:22:14.320> you<00:22:14.400> want<00:22:14.520> to<00:22:14.679> continue<00:22:15.400> do<00:22:15.559> you<00:22:15.679> want 00:22:15.750 --> 00:22:15.760 align:start position:0% says do you want to continue do you want 00:22:15.760 --> 00:22:19.750 align:start position:0% says do you want to continue do you want to<00:22:15.960> go<00:22:16.200> down<00:22:17.200> uh<00:22:17.360> the<00:22:17.720> trees<00:22:18.720> um<00:22:18.960> now<00:22:19.200> this<00:22:19.440> Tree 00:22:19.750 --> 00:22:19.760 align:start position:0% to go down uh the trees um now this Tree 00:22:19.760 --> 00:22:23.630 align:start position:0% to go down uh the trees um now this Tree Visitor<00:22:20.720> uh<00:22:21.720> these 00:22:23.630 --> 00:22:23.640 align:start position:0% Visitor uh these 00:22:23.640 --> 00:22:25.909 align:start position:0% Visitor uh these um<00:22:24.640> solution 00:22:25.909 --> 00:22:25.919 align:start position:0% um solution 00:22:25.919 --> 00:22:30.350 align:start position:0% um solution these<00:22:26.919> Slither<00:22:27.600> May<00:22:28.039> well<00:22:28.760> um<00:22:29.400> solve<00:22:29.880> the<00:22:30.039> same 00:22:30.350 --> 00:22:30.360 align:start position:0% these Slither May well um solve the same 00:22:30.360 --> 00:22:32.830 align:start position:0% these Slither May well um solve the same kind<00:22:30.559> of<00:22:30.799> problem<00:22:31.520> we<00:22:31.760> have<00:22:32.080> a<00:22:32.320> different<00:22:32.640> set 00:22:32.830 --> 00:22:32.840 align:start position:0% kind of problem we have a different set 00:22:32.840 --> 00:22:35.269 align:start position:0% kind of problem we have a different set of<00:22:33.039> constraints<00:22:34.039> for<00:22:34.200> example<00:22:34.600> our<00:22:34.840> query 00:22:35.269 --> 00:22:35.279 align:start position:0% of constraints for example our query 00:22:35.279 --> 00:22:39.310 align:start position:0% of constraints for example our query language<00:22:36.279> uh<00:22:36.480> is<00:22:36.840> intended<00:22:37.279> to<00:22:37.440> be<00:22:38.320> extended 00:22:39.310 --> 00:22:39.320 align:start position:0% language uh is intended to be extended 00:22:39.320 --> 00:22:41.990 align:start position:0% language uh is intended to be extended with<00:22:39.640> semantic<00:22:40.440> predicates<00:22:41.440> and<00:22:41.640> with<00:22:41.799> the 00:22:41.990 --> 00:22:42.000 align:start position:0% with semantic predicates and with the 00:22:42.000 --> 00:22:44.029 align:start position:0% with semantic predicates and with the ability<00:22:42.400> to<00:22:42.600> do<00:22:42.840> arbitrary<00:22:43.360> recursion<00:22:43.919> by 00:22:44.029 --> 00:22:44.039 align:start position:0% ability to do arbitrary recursion by 00:22:44.039 --> 00:22:47.470 align:start position:0% ability to do arbitrary recursion by skipping<00:22:44.480> over<00:22:45.120> arbitrary<00:22:46.120> subtes<00:22:47.120> uh<00:22:47.279> so 00:22:47.470 --> 00:22:47.480 align:start position:0% skipping over arbitrary subtes uh so 00:22:47.480 --> 00:22:49.070 align:start position:0% skipping over arbitrary subtes uh so there's<00:22:47.679> a<00:22:47.840> lot<00:22:48.120> that<00:22:48.240> we<00:22:48.360> want<00:22:48.480> to<00:22:48.640> do<00:22:48.880> there 00:22:49.070 --> 00:22:49.080 align:start position:0% there's a lot that we want to do there 00:22:49.080 --> 00:22:52.070 align:start position:0% there's a lot that we want to do there so<00:22:49.440> I<00:22:49.559> wouldn't<00:22:49.919> say<00:22:50.320> that<00:22:51.200> that<00:22:51.640> um<00:22:51.880> in 00:22:52.070 --> 00:22:52.080 align:start position:0% so I wouldn't say that that um in 00:22:52.080 --> 00:22:54.549 align:start position:0% so I wouldn't say that that um in slyther<00:22:52.720> you<00:22:52.960> can<00:22:53.200> or<00:22:53.400> cannot<00:22:53.720> do<00:22:53.919> that<00:22:54.400> I'm 00:22:54.549 --> 00:22:54.559 align:start position:0% slyther you can or cannot do that I'm 00:22:54.559 --> 00:22:57.710 align:start position:0% slyther you can or cannot do that I'm not<00:22:54.760> familiar<00:22:55.240> enough<00:22:55.720> with<00:22:56.320> slither<00:22:57.320> perfect 00:22:57.710 --> 00:22:57.720 align:start position:0% not familiar enough with slither perfect 00:22:57.720 --> 00:22:58.990 align:start position:0% not familiar enough with slither perfect thank<00:22:57.840> you<00:22:58.039> is<00:22:58.120> there<00:22:58.240> a<00:22:58.320> question<00:22:58.679> you<00:22:58.799> like 00:22:58.990 --> 00:22:59.000 align:start position:0% thank you is there a question you like 00:22:59.000 --> 00:23:01.830 align:start position:0% thank you is there a question you like most<00:22:59.240> in 00:23:01.830 --> 00:23:01.840 align:start position:0% 00:23:01.840 --> 00:23:04.190 align:start position:0% there<00:23:02.840> uh<00:23:02.960> well<00:23:03.120> will<00:23:03.360> this<00:23:03.720> work<00:23:04.000> with 00:23:04.190 --> 00:23:04.200 align:start position:0% there uh well will this work with 00:23:04.200 --> 00:23:05.990 align:start position:0% there uh well will this work with different<00:23:04.480> evm<00:23:04.960> versions<00:23:05.520> yes<00:23:05.640> it<00:23:05.760> will 00:23:05.990 --> 00:23:06.000 align:start position:0% different evm versions yes it will 00:23:06.000 --> 00:23:07.230 align:start position:0% different evm versions yes it will because<00:23:06.200> we're<00:23:06.320> dealing<00:23:06.600> with<00:23:06.720> Source<00:23:07.039> where 00:23:07.230 --> 00:23:07.240 align:start position:0% because we're dealing with Source where 00:23:07.240 --> 00:23:10.310 align:start position:0% because we're dealing with Source where well<00:23:07.480> before<00:23:07.760> evm<00:23:08.440> slang<00:23:08.840> is<00:23:09.000> a<00:23:09.520> compiler<00:23:10.200> and 00:23:10.310 --> 00:23:10.320 align:start position:0% well before evm slang is a compiler and 00:23:10.320 --> 00:23:12.029 align:start position:0% well before evm slang is a compiler and it'll<00:23:10.640> produce<00:23:11.120> bite<00:23:11.400> code<00:23:11.640> so<00:23:11.799> that's<00:23:11.919> a 00:23:12.029 --> 00:23:12.039 align:start position:0% it'll produce bite code so that's a 00:23:12.039 --> 00:23:13.789 align:start position:0% it'll produce bite code so that's a question<00:23:12.320> about<00:23:12.520> the<00:23:12.679> compiler<00:23:13.320> not<00:23:13.480> about 00:23:13.789 --> 00:23:13.799 align:start position:0% question about the compiler not about 00:23:13.799 --> 00:23:16.029 align:start position:0% question about the compiler not about querying<00:23:14.799> have<00:23:14.919> we<00:23:15.159> published<00:23:15.600> the<00:23:15.720> grammar 00:23:16.029 --> 00:23:16.039 align:start position:0% querying have we published the grammar 00:23:16.039 --> 00:23:18.990 align:start position:0% querying have we published the grammar for<00:23:16.200> slang<00:23:16.880> yes<00:23:17.120> we<00:23:17.320> have<00:23:18.240> uh<00:23:18.360> slang<00:23:18.799> is 00:23:18.990 --> 00:23:19.000 align:start position:0% for slang yes we have uh slang is 00:23:19.000 --> 00:23:23.590 align:start position:0% for slang yes we have uh slang is actually<00:23:19.640> a<00:23:20.640> uh<00:23:20.960> declarative<00:23:21.960> meta<00:23:22.679> project 00:23:23.590 --> 00:23:23.600 align:start position:0% actually a uh declarative meta project 00:23:23.600 --> 00:23:26.070 align:start position:0% actually a uh declarative meta project so<00:23:23.880> you<00:23:24.039> can<00:23:24.240> use<00:23:24.400> it<00:23:24.520> for<00:23:24.720> any<00:23:25.600> programming 00:23:26.070 --> 00:23:26.080 align:start position:0% so you can use it for any programming 00:23:26.080 --> 00:23:29.350 align:start position:0% so you can use it for any programming language<00:23:26.480> not<00:23:26.720> just<00:23:27.120> solidity<00:23:28.120> and<00:23:28.520> we<00:23:28.679> have 00:23:29.350 --> 00:23:29.360 align:start position:0% language not just solidity and we have 00:23:29.360 --> 00:23:31.149 align:start position:0% language not just solidity and we have um<00:23:29.559> published<00:23:29.960> that<00:23:30.200> everything<00:23:30.520> we<00:23:30.640> do<00:23:30.880> is 00:23:31.149 --> 00:23:31.159 align:start position:0% um published that everything we do is 00:23:31.159 --> 00:23:33.549 align:start position:0% um published that everything we do is open<00:23:31.679> source<00:23:32.679> uh 00:23:33.549 --> 00:23:33.559 align:start position:0% open source uh 00:23:33.559 --> 00:23:37.230 align:start position:0% open source uh nomic<00:23:34.559> foundation<00:23:35.440> on<00:23:35.799> GitHub<00:23:36.799> all<00:23:36.960> of<00:23:37.080> our 00:23:37.230 --> 00:23:37.240 align:start position:0% nomic foundation on GitHub all of our 00:23:37.240 --> 00:23:39.190 align:start position:0% nomic foundation on GitHub all of our development<00:23:37.760> is<00:23:37.880> in<00:23:38.039> the<00:23:38.200> open<00:23:38.520> you<00:23:38.640> can<00:23:38.799> reuse 00:23:39.190 --> 00:23:39.200 align:start position:0% development is in the open you can reuse 00:23:39.200 --> 00:23:42.669 align:start position:0% development is in the open you can reuse all<00:23:39.360> of<00:23:39.600> this 00:23:42.669 --> 00:23:42.679 align:start position:0% 00:23:42.679 --> 00:23:46.549 align:start position:0% awesome<00:23:43.679> uh<00:23:43.880> how<00:23:44.120> important<00:23:44.679> well<00:23:45.120> uh<00:23:45.400> so<00:23:46.400> how 00:23:46.549 --> 00:23:46.559 align:start position:0% awesome uh how important well uh so how 00:23:46.559 --> 00:23:48.190 align:start position:0% awesome uh how important well uh so how important<00:23:46.880> is<00:23:47.000> it<00:23:47.120> to<00:23:47.240> maintain<00:23:47.640> code<00:23:48.000> with 00:23:48.190 --> 00:23:48.200 align:start position:0% important is it to maintain code with 00:23:48.200 --> 00:23:50.110 align:start position:0% important is it to maintain code with different<00:23:48.520> solidity<00:23:49.039> versions<00:23:49.600> why<00:23:49.799> why<00:23:49.919> not 00:23:50.110 --> 00:23:50.120 align:start position:0% different solidity versions why why not 00:23:50.120 --> 00:23:53.149 align:start position:0% different solidity versions why why not just<00:23:50.320> use<00:23:50.559> one<00:23:50.919> version<00:23:51.919> because<00:23:52.559> if<00:23:52.720> you<00:23:53.000> want 00:23:53.149 --> 00:23:53.159 align:start position:0% just use one version because if you want 00:23:53.159 --> 00:23:55.909 align:start position:0% just use one version because if you want to<00:23:53.640> be<00:23:53.799> able<00:23:54.039> to<00:23:54.240> provide<00:23:54.559> tools<00:23:54.919> that<00:23:55.120> analyze 00:23:55.909 --> 00:23:55.919 align:start position:0% to be able to provide tools that analyze 00:23:55.919 --> 00:23:59.549 align:start position:0% to be able to provide tools that analyze a<00:23:56.080> large<00:23:56.400> number<00:23:56.640> of<00:23:57.039> contracts<00:23:58.039> which<00:23:58.760> may<00:23:59.200> be 00:23:59.549 --> 00:23:59.559 align:start position:0% a large number of contracts which may be 00:23:59.559 --> 00:24:02.549 align:start position:0% a large number of contracts which may be an<00:23:59.760> earlier<00:24:00.480> version<00:24:01.039> of<00:24:01.240> solidity<00:24:02.240> than<00:24:02.440> the 00:24:02.549 --> 00:24:02.559 align:start position:0% an earlier version of solidity than the 00:24:02.559 --> 00:24:04.669 align:start position:0% an earlier version of solidity than the latest<00:24:02.960> one<00:24:03.520> for<00:24:03.720> example 00:24:04.669 --> 00:24:04.679 align:start position:0% latest one for example 00:24:04.679 --> 00:24:07.909 align:start position:0% latest one for example 0411<00:24:05.679> there's<00:24:05.880> a<00:24:06.080> a<00:24:06.240> contract<00:24:06.919> on<00:24:07.080> mainnet 00:24:07.909 --> 00:24:07.919 align:start position:0% 0411 there's a a contract on mainnet 00:24:07.919 --> 00:24:09.870 align:start position:0% 0411 there's a a contract on mainnet that<00:24:08.039> is<00:24:08.200> 0411<00:24:09.080> you<00:24:09.159> want<00:24:09.240> to<00:24:09.360> get<00:24:09.480> the<00:24:09.600> source 00:24:09.870 --> 00:24:09.880 align:start position:0% that is 0411 you want to get the source 00:24:09.880 --> 00:24:12.390 align:start position:0% that is 0411 you want to get the source to<00:24:10.080> that<00:24:10.480> you<00:24:10.600> want<00:24:10.760> to<00:24:11.320> um<00:24:11.520> provide<00:24:11.880> analysis 00:24:12.390 --> 00:24:12.400 align:start position:0% to that you want to um provide analysis 00:24:12.400 --> 00:24:14.669 align:start position:0% to that you want to um provide analysis tools<00:24:12.760> for<00:24:12.960> it<00:24:13.799> that's<00:24:13.960> why<00:24:14.080> we<00:24:14.200> want<00:24:14.320> to 00:24:14.669 --> 00:24:14.679 align:start position:0% tools for it that's why we want to 00:24:14.679 --> 00:24:16.710 align:start position:0% tools for it that's why we want to support<00:24:15.000> all<00:24:15.120> of<00:24:15.279> these<00:24:15.480> versions<00:24:16.320> now<00:24:16.600> we 00:24:16.710 --> 00:24:16.720 align:start position:0% support all of these versions now we 00:24:16.720 --> 00:24:19.390 align:start position:0% support all of these versions now we don't<00:24:16.960> go<00:24:17.159> back<00:24:17.360> to<00:24:18.000> 001<00:24:18.840> or<00:24:19.000> whatever<00:24:19.279> the 00:24:19.390 --> 00:24:19.400 align:start position:0% don't go back to 001 or whatever the 00:24:19.400 --> 00:24:21.710 align:start position:0% don't go back to 001 or whatever the first<00:24:19.679> version<00:24:20.080> was<00:24:20.640> so<00:24:20.880> we're<00:24:21.159> pragmatic 00:24:21.710 --> 00:24:21.720 align:start position:0% first version was so we're pragmatic 00:24:21.720 --> 00:24:23.950 align:start position:0% first version was so we're pragmatic about<00:24:21.919> it<00:24:22.559> but<00:24:22.960> these<00:24:23.120> are<00:24:23.320> the<00:24:23.480> versions<00:24:23.840> that 00:24:23.950 --> 00:24:23.960 align:start position:0% about it but these are the versions that 00:24:23.960 --> 00:24:26.149 align:start position:0% about it but these are the versions that are<00:24:24.200> live<00:24:24.919> and<00:24:25.039> our<00:24:25.240> goal<00:24:25.440> is<00:24:25.559> to<00:24:25.720> support<00:24:26.039> all 00:24:26.149 --> 00:24:26.159 align:start position:0% are live and our goal is to support all 00:24:26.159 --> 00:24:27.750 align:start position:0% are live and our goal is to support all the<00:24:26.279> versions<00:24:26.640> that<00:24:26.720> are<00:24:26.919> live<00:24:27.360> how<00:24:27.480> do<00:24:27.600> you 00:24:27.750 --> 00:24:27.760 align:start position:0% the versions that are live how do you 00:24:27.760 --> 00:24:29.549 align:start position:0% the versions that are live how do you determine<00:24:28.159> the<00:24:28.399> cut<00:24:28.600> off 00:24:29.549 --> 00:24:29.559 align:start position:0% determine the cut off 00:24:29.559 --> 00:24:33.669 align:start position:0% determine the cut off version<00:24:30.559> uh<00:24:31.039> what's<00:24:32.000> analysis<00:24:33.000> an<00:24:33.240> analysis 00:24:33.669 --> 00:24:33.679 align:start position:0% version uh what's analysis an analysis 00:24:33.679 --> 00:24:35.710 align:start position:0% version uh what's analysis an analysis of<00:24:33.919> the<00:24:34.240> of<00:24:34.440> m<00:24:34.720> net<00:24:34.880> and<00:24:34.960> all<00:24:35.080> the<00:24:35.240> contracts 00:24:35.710 --> 00:24:35.720 align:start position:0% of the of m net and all the contracts 00:24:35.720 --> 00:24:37.750 align:start position:0% of the of m net and all the contracts that<00:24:35.840> are<00:24:36.039> live<00:24:36.880> okay<00:24:37.000> is<00:24:37.080> it<00:24:37.240> the<00:24:37.360> number<00:24:37.600> of 00:24:37.750 --> 00:24:37.760 align:start position:0% that are live okay is it the number of 00:24:37.760 --> 00:24:39.669 align:start position:0% that are live okay is it the number of contract<00:24:38.240> is<00:24:38.320> it<00:24:38.480> the<00:24:38.640> value<00:24:38.960> stored<00:24:39.279> in<00:24:39.480> those 00:24:39.669 --> 00:24:39.679 align:start position:0% contract is it the value stored in those 00:24:39.679 --> 00:24:41.590 align:start position:0% contract is it the value stored in those is<00:24:39.760> it<00:24:39.880> the<00:24:40.000> amount<00:24:40.200> of<00:24:40.360> transactions<00:24:41.279> no<00:24:41.480> the 00:24:41.590 --> 00:24:41.600 align:start position:0% is it the amount of transactions no the 00:24:41.600 --> 00:24:44.669 align:start position:0% is it the amount of transactions no the earliest<00:24:42.520> the<00:24:43.039> um<00:24:43.960> I<00:24:44.080> didn't<00:24:44.360> do<00:24:44.520> this 00:24:44.669 --> 00:24:44.679 align:start position:0% earliest the um I didn't do this 00:24:44.679 --> 00:24:46.549 align:start position:0% earliest the um I didn't do this analysis<00:24:45.159> so<00:24:45.320> I<00:24:45.399> must<00:24:45.640> admit<00:24:45.960> I<00:24:46.039> don't<00:24:46.200> know 00:24:46.549 --> 00:24:46.559 align:start position:0% analysis so I must admit I don't know 00:24:46.559 --> 00:24:48.909 align:start position:0% analysis so I must admit I don't know what<00:24:47.039> process<00:24:47.399> we<00:24:47.559> use<00:24:47.799> to<00:24:47.960> determine<00:24:48.440> that 00:24:48.909 --> 00:24:48.919 align:start position:0% what process we use to determine that 00:24:48.919 --> 00:24:50.710 align:start position:0% what process we use to determine that but<00:24:49.120> it<00:24:49.240> is<00:24:49.440> the<00:24:49.600> case<00:24:49.919> that<00:24:50.039> the<00:24:50.200> earliest 00:24:50.710 --> 00:24:50.720 align:start position:0% but it is the case that the earliest 00:24:50.720 --> 00:24:54.070 align:start position:0% but it is the case that the earliest contract<00:24:51.480> in<00:24:51.679> use<00:24:52.000> apparently<00:24:52.679> is<00:24:53.080> 0411 00:24:54.070 --> 00:24:54.080 align:start position:0% contract in use apparently is 0411 00:24:54.080 --> 00:24:57.149 align:start position:0% contract in use apparently is 0411 fantastic<00:24:54.640> thank<00:24:55.159> you<00:24:56.159> um<00:24:56.360> what's<00:24:56.520> the<00:24:56.960> best 00:24:57.149 --> 00:24:57.159 align:start position:0% fantastic thank you um what's the best 00:24:57.159 --> 00:24:58.950 align:start position:0% fantastic thank you um what's the best practice<00:24:57.440> for<00:24:57.600> using<00:24:57.840> slang<00:24:58.159> to<00:24:58.440> analyze<00:24:58.799> a 00:24:58.950 --> 00:24:58.960 align:start position:0% practice for using slang to analyze a 00:24:58.960 --> 00:25:00.630 align:start position:0% practice for using slang to analyze a large<00:24:59.200> number<00:24:59.440> of<00:24:59.640> program<00:25:00.159> where<00:25:00.279> should<00:25:00.480> the 00:25:00.630 --> 00:25:00.640 align:start position:0% large number of program where should the 00:25:00.640 --> 00:25:02.590 align:start position:0% large number of program where should the data<00:25:00.880> be<00:25:01.000> stored<00:25:01.320> and<00:25:01.440> in<00:25:01.600> what<00:25:01.799> format 00:25:02.590 --> 00:25:02.600 align:start position:0% data be stored and in what format 00:25:02.600 --> 00:25:03.669 align:start position:0% data be stored and in what format imagine<00:25:02.919> this<00:25:03.039> is<00:25:03.159> something<00:25:03.360> you<00:25:03.480> run 00:25:03.669 --> 00:25:03.679 align:start position:0% imagine this is something you run 00:25:03.679 --> 00:25:06.470 align:start position:0% imagine this is something you run locally<00:25:04.159> correct<00:25:04.960> yes<00:25:05.120> it<00:25:05.320> is<00:25:05.840> perfect<00:25:06.279> thank 00:25:06.470 --> 00:25:06.480 align:start position:0% locally correct yes it is perfect thank 00:25:06.480 --> 00:25:08.909 align:start position:0% locally correct yes it is perfect thank you<00:25:07.080> all<00:25:07.240> right<00:25:07.840> what<00:25:08.039> update<00:25:08.320> in<00:25:08.480> solidity 00:25:08.909 --> 00:25:08.919 align:start position:0% you all right what update in solidity 00:25:08.919 --> 00:25:11.190 align:start position:0% you all right what update in solidity was<00:25:09.120> the<00:25:09.240> artist<00:25:09.640> to<00:25:09.880> that<00:25:10.080> for<00:25:10.320> you<00:25:10.399> mentioned 00:25:11.190 --> 00:25:11.200 align:start position:0% was the artist to that for you mentioned 00:25:11.200 --> 00:25:13.789 align:start position:0% was the artist to that for you mentioned quirks<00:25:11.799> and<00:25:12.200> weird<00:25:12.600> updates<00:25:12.960> in<00:25:13.080> solidity 00:25:13.789 --> 00:25:13.799 align:start position:0% quirks and weird updates in solidity 00:25:13.799 --> 00:25:16.070 align:start position:0% quirks and weird updates in solidity which<00:25:13.919> one<00:25:14.159> was<00:25:14.480> the<00:25:14.720> hardest 00:25:16.070 --> 00:25:16.080 align:start position:0% which one was the hardest 00:25:16.080 --> 00:25:20.190 align:start position:0% which one was the hardest or<00:25:17.080> none<00:25:17.279> of<00:25:17.480> them<00:25:17.760> was<00:25:18.039> particularly<00:25:19.039> hard<00:25:20.039> uh 00:25:20.190 --> 00:25:20.200 align:start position:0% or none of them was particularly hard uh 00:25:20.200 --> 00:25:22.789 align:start position:0% or none of them was particularly hard uh the<00:25:20.399> volume<00:25:20.760> of<00:25:20.960> quirks<00:25:21.960> is<00:25:22.360> what<00:25:22.520> is<00:25:22.640> a 00:25:22.789 --> 00:25:22.799 align:start position:0% the volume of quirks is what is a 00:25:22.799 --> 00:25:24.870 align:start position:0% the volume of quirks is what is a challenge<00:25:23.600> I<00:25:23.679> mean<00:25:23.960> we've<00:25:24.399> we've<00:25:24.600> got 00:25:24.870 --> 00:25:24.880 align:start position:0% challenge I mean we've we've got 00:25:24.880 --> 00:25:27.470 align:start position:0% challenge I mean we've we've got hundreds<00:25:25.399> of<00:25:25.600> edge<00:25:25.960> cases<00:25:26.679> we<00:25:26.799> had<00:25:26.919> to<00:25:27.080> analyze 00:25:27.470 --> 00:25:27.480 align:start position:0% hundreds of edge cases we had to analyze 00:25:27.480 --> 00:25:29.430 align:start position:0% hundreds of edge cases we had to analyze Sal<00:25:27.840> C<00:25:28.039> because<00:25:28.399> that's<00:25:28.600> the<00:25:28.720> only<00:25:29.039> definition 00:25:29.430 --> 00:25:29.440 align:start position:0% Sal C because that's the only definition 00:25:29.440 --> 00:25:32.350 align:start position:0% Sal C because that's the only definition of<00:25:29.559> the<00:25:30.000> language<00:25:31.000> uh<00:25:31.399> and<00:25:31.840> go<00:25:32.039> through<00:25:32.200> the 00:25:32.350 --> 00:25:32.360 align:start position:0% of the language uh and go through the 00:25:32.360 --> 00:25:34.510 align:start position:0% of the language uh and go through the code<00:25:33.000> and<00:25:33.120> then<00:25:33.279> test<00:25:33.559> it<00:25:34.000> and<00:25:34.080> then<00:25:34.200> go<00:25:34.320> to 00:25:34.510 --> 00:25:34.520 align:start position:0% code and then test it and then go to 00:25:34.520 --> 00:25:37.350 align:start position:0% code and then test it and then go to sanctuary<00:25:35.360> and<00:25:35.520> look<00:25:35.640> at<00:25:35.919> massive<00:25:36.919> uh<00:25:37.039> numbers 00:25:37.350 --> 00:25:37.360 align:start position:0% sanctuary and look at massive uh numbers 00:25:37.360 --> 00:25:38.590 align:start position:0% sanctuary and look at massive uh numbers of 00:25:38.590 --> 00:25:38.600 align:start position:0% of 00:25:38.600 --> 00:25:41.909 align:start position:0% of contracts<00:25:39.600> uh<00:25:39.760> run<00:25:40.520> uh<00:25:40.679> our<00:25:40.919> compiler<00:25:41.640> over 00:25:41.909 --> 00:25:41.919 align:start position:0% contracts uh run uh our compiler over 00:25:41.919 --> 00:25:43.830 align:start position:0% contracts uh run uh our compiler over them<00:25:42.080> or<00:25:42.240> run<00:25:42.440> our<00:25:42.600> paer<00:25:43.039> over<00:25:43.240> them<00:25:43.640> what 00:25:43.830 --> 00:25:43.840 align:start position:0% them or run our paer over them what 00:25:43.840 --> 00:25:46.990 align:start position:0% them or run our paer over them what breaks<00:25:44.520> what<00:25:44.720> doesn't<00:25:45.360> we've<00:25:45.559> got<00:25:46.000> extensive 00:25:46.990 --> 00:25:47.000 align:start position:0% breaks what doesn't we've got extensive 00:25:47.000 --> 00:25:49.710 align:start position:0% breaks what doesn't we've got extensive uh<00:25:47.159> test<00:25:47.559> cases<00:25:48.480> so<00:25:48.880> that<00:25:49.000> was<00:25:49.159> the<00:25:49.320> challenge 00:25:49.710 --> 00:25:49.720 align:start position:0% uh test cases so that was the challenge 00:25:49.720 --> 00:25:52.110 align:start position:0% uh test cases so that was the challenge it's<00:25:49.919> the<00:25:50.080> number<00:25:50.559> not<00:25:51.080> not<00:25:51.279> any<00:25:51.520> particular 00:25:52.110 --> 00:25:52.120 align:start position:0% it's the number not not any particular 00:25:52.120 --> 00:25:53.830 align:start position:0% it's the number not not any particular difficulty<00:25:52.520> fantastic<00:25:53.240> thank<00:25:53.440> you<00:25:53.600> do<00:25:53.720> you 00:25:53.830 --> 00:25:53.840 align:start position:0% difficulty fantastic thank you do you 00:25:53.840 --> 00:25:56.830 align:start position:0% difficulty fantastic thank you do you dream<00:25:54.120> in<00:25:54.320> bite<00:25:54.679> code<00:25:55.679> uh<00:25:55.880> no<00:25:56.399> no<00:25:56.559> I<00:25:56.679> don't 00:25:56.830 --> 00:25:56.840 align:start position:0% dream in bite code uh no no I don't 00:25:56.840 --> 00:25:59.549 align:start position:0% dream in bite code uh no no I don't dream<00:25:57.279> I<00:25:57.360> dream<00:25:57.679> compilers<00:25:58.520> actually<00:25:59.480> all 00:25:59.549 --> 00:25:59.559 align:start position:0% dream I dream compilers actually all 00:25:59.559 --> 00:26:00.909 align:start position:0% dream I dream compilers actually all right<00:25:59.720> Anthony<00:26:00.080> thank<00:26:00.200> you<00:26:00.320> a<00:26:00.399> lot<00:26:00.559> for<00:26:00.679> your 00:26:00.909 --> 00:26:00.919 align:start position:0% right Anthony thank you a lot for your 00:26:00.919 --> 00:26:03.990 align:start position:0% right Anthony thank you a lot for your time<00:26:01.200> and<00:26:01.360> all<00:26:01.480> the<00:26:01.600> best<00:26:01.760> to<00:26:01.880> you<00:26:02.760> thank<00:26:03.000> you 00:26:03.990 --> 00:26:04.000 align:start position:0% time and all the best to you thank you 00:26:04.000 --> 00:26:06.389 align:start position:0% time and all the best to you thank you people<00:26:04.520> our<00:26:04.880> next<00:26:05.159> session<00:26:05.640> will<00:26:05.799> start<00:26:06.080> in<00:26:06.279> a 00:26:06.389 --> 00:26:06.399 align:start position:0% people our next session will start in a 00:26:06.399 --> 00:26:09.350 align:start position:0% people our next session will start in a few<00:26:06.600> minutes<00:26:07.320> I<00:26:07.440> am<00:26:07.840> off<00:26:08.240> for<00:26:08.520> today<00:26:09.000> thank<00:26:09.200> you 00:26:09.350 --> 00:26:09.360 align:start position:0% few minutes I am off for today thank you 00:26:09.360 --> 00:26:10.909 align:start position:0% few minutes I am off for today thank you for<00:26:09.679> those<00:26:09.840> who<00:26:10.000> spent<00:26:10.200> a<00:26:10.279> bit<00:26:10.440> of<00:26:10.600> time<00:26:10.760> with 00:26:10.909 --> 00:26:10.919 align:start position:0% for those who spent a bit of time with 00:26:10.919 --> 00:26:16.000 align:start position:0% for those who spent a bit of time with me<00:26:11.320> this<00:26:11.799> morning<00:26:12.799> um<00:26:13.080> and<00:26:13.240> I'll<00:26:13.399> see<00:26:13.559> you<00:26:13.640> soon